Transmitting/receiving system and method for processing a broadcast signal

ABSTRACT

According to the present invention, a method for processing a broadcast signal in a transmitting system that transmits an emergency alert message through a mobile broadcast network comprises the steps of: RS-CRC encoding of mobile service data containing an emergency alert message so as to generate an RS frame that belongs to an ensemble; dividing the RS frame into a plurality of RS frame portions; mapping the plurality of RS frame portions to data groups and inserting one FIC segment, TPC data, and a plurality of base data streams into each data group; trellis-encoding the data of the data groups; and transmitting a broadcast signal comprising the trellis-encoded data. At least one of either a FIC segment header contained in the FIC segment or the TPC data includes wake-up indication information for compulsorily placing a broadcast receiver into an active mode depending on the level of seriousness of the emergency alert message.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is the National Phase of PCT/KR2012/004167 filed on May25, 2012, which claims priority under 35 U.S.C. 119(e) to U.S.Provisional Application No. 61/489,683 filed on May 25, 2011, to U.S.Provisional Application No. 61/493,964 filed on Jun. 6, 2011 and to U.S.Provisional Application No. 61/505,512 filed on Jul. 7, 2011, all ofwhich are incorporated by reference herein in its entirety.

TECHNICAL FIELD

The present invention relates to a digital broadcasting system fortransmitting and receiving digital broadcast signal, and moreparticularly, to a transmitting system for processing and transmittingdigital broadcast signal, and a receiving system for receiving andprocessing digital broadcast signal and, a method of processing digitalbroadcast signal in the transmitting system and the receiving system.

BACKGROUND ART

The Vestigial Sideband (VSB) transmission mode, which is adopted as thestandard for digital broadcasting in North America and the Republic ofKorea, is a system using a single carrier method. Therefore, thereceiving performance of the digital broadcast receiving system may bedeteriorated in a poor channel environment. Particularly, sinceresistance to changes in channels and noise is more highly required whenusing portable and/or mobile broadcast receivers, the receivingperformance may be even more deteriorated when transmitting mobileservice data by the VSB transmission mode.

DISCLOSURE Technical Problem

An object of the present invention is to provide a transmitting systemand a receiving system and a method of processing broadcast signal thatare highly resistant to channel changes and noise.

Another object of the present invention is to provide a transmittingsystem and a receiving system and a method of processing broadcastsignal that can enhance the receiving performance of the receivingsystem by performing additional encoding on mobile service data and bytransmitting the processed data to the receiving system.

A further object of the present invention is to provide a transmittingsystem and a receiving system and a method of processing broadcastsignal that can also enhance the receiving performance of the receivingsystem by inserting known data already known in accordance with apre-agreement between the receiving system and the transmitting systemin a predetermined region within a data region.

Yet another object of the present invention is to provide a transmittingsystem, a receiving system, and a method of processing a broadcastsignal that may allow the transmitting system to signal and transmitinformation identifying an enhancement service, and that may then allowthe receiving system to use the transmitted information so as to supportto the enhancement service.

Another object of the present invention is to provide a transmittingsystem and a receiving system and a method of processing broadcastsignals that allow the receiving system capable of receiving mobilebroadcasts to provide a disaster alert service by transmitting anemergency alert message using a mobile broadcast network.

Another object of the present invention is to provide a signaling methodand transmission/reception method for signaling information that allowthe receiving system capable of receiving mobile broadcast to providethe disaster alert service.

Another object of the present invention is to provide a transmittingsystem and a receiving system and a method of processing broadcastsignals which can efficiently provide a disaster alert service byproviding additional information associated with the emergency alertmessage.

Technical Solution

The object of the present invention can be achieved by providing amethod for processing a broadcast signal in a transmitting systemincluding the steps of performing Reed Solomon-Cyclic Redundancy Check(RS-CRC) encoding on mobile service data containing an emergency alertmessage and generating an RS frame belonging to an ensemble, dividingthe RS frame into a plurality of RS frame portions, mapping the RS frameportions into respective data groups and inserting one fast informationchannel (FIC) segment and a plurality of known data sequences into eachof the data groups, performing trellis encoding on data of the datagroups, and transmitting the broadcast signal including thetrellis-encoded data.

An FIC chunk is configured with an FIC chunk header and FIC chunkpayload, signals biding information between the ensemble and a mobileservice included in the ensemble, and is divided into a plurality of FICsegment payloads. The FIC segment is configured with an FIC segmentheader and one of the plurality of FIC segment payloads.

The FIC segment header includes wake-up indication information forcompulsorily switching a broadcast receiver to an active mode accordingto a degree of severity of the emergency alert message.

The emergency alert message may be transmitted in a Common AlertingProtocol (CAP) form or a syntax form.

The ensemble may include at least one of a service map table (SMT) andan emergency alert table (EAT). Each of the SMT and the EAT comprises anensemble identifier to identify the ensemble. Identifying informationfor identifying whether the emergency alert message is in the CAP formor in the syntax form may be signaled to at least one of the SMT and theEAT.

IP datagrams including the SMT and IP datagrams including the EAT may betransmitted over a service signaling channel. All the IP datagramstransmitted over the service signaling channel may have the samewell-known IP address and the same well-known UDP port number.

The FIC chunk payload may include the ensemble identifier to identifythe ensemble and indication information to indicate whether the EAT istransmitted over a service signaling channel included in the ensemble.

The method may further include the step of including disaster-relatedadditional information associated with the emergency alert message in atleast one file and transmitting the at least file including thedisaster-related additional information in non-real time (NRT).

In another aspect of the present invention, provided herein is atransmitting system including a first encoder configured to perform ReedSolomon-Cyclic Redundancy Check (RS-CRC) encoding on mobile service datacontaining an emergency alert message and generate an RS frame belongingto an ensemble, a divider configured to divide the RS frame into aplurality of RS frame portions, a group formatter configured to map theRS frame portions into respective data groups and insert one fastinformation channel (FIC) segment and a plurality of known datasequences into each of the data groups, a second encoder configured toperform trellis encoding on data of the data groups, and a transmittingunit configured to transmit a broadcast signal including thetrellis-encoded data.

An FIC chunk is configured with an FIC chunk header and FIC chunkpayload, signals biding information between the ensemble and a mobileservice included in the ensemble, and is divided into a plurality of FICsegment payloads. The FIC segment may be configured with an FIC segmentheader and one of the plurality of FIC segment payloads. The FIC segmentheader may include wake-up indication information for compulsorilyswitching a broadcast receiver to an active mode according to a degreeof severity of the emergency alert message.

Other objects, features and advantages of the invention will be apparentfrom a detailed description of embodiments with reference to theaccompanying drawings.

Advantageous Effects

As described above, the transmitting system and the receiving system andthe broadcast signal processing method of the same according to thepresent invention have the following advantages. When transmittingmobile service data through a channel, the present invention may berobust against errors and backward compatible with the conventionaldigital broadcast receiving system.

Moreover, the present invention may also receive the mobile service datawithout any error even in channels having severe ghost effect and noise.

Furthermore, by inserting known data in a particular position (or place)within a data region and transmitting the processed data, the receivingperformance of the receiving system may be enhanced even in a channelenvironment that is liable to frequent changes.

In addition, by transmitting an emergency alert message using a mobilebroadcast network in a mobile broadcast transmitter and, receiving andprocessing it by a mobile broadcast receiver, the broadcast receivercapable of receiving mobile broadcasts can provide a disaster alertservice to a viewer.

Also, by transmitting and receiving additional information associatedwith the emergency alert message in non-real time and then by servicingto viewers, the disaster alert service can be serviced efficientlythrough mobile broadcast.

Finally, the present invention is even more effective when applied tomobile and portable receivers, which are also liable to a frequentchange in channel and which require protection (or resistance) againstintense noise.

DESCRIPTION OF DRAWINGS

FIG. 1 illustrates a structure of a M/H frame for transmitting andreceiving mobile service data according to the present invention;

FIG. 2 illustrates an exemplary structure of a VSB frame;

FIG. 3 illustrates a mapping example of the positions to which the first4 slots of a sub-frame are assigned with respect to a VSB frame in aspace region;

FIG. 4 illustrates a mapping example of the positions to which the first4 slots of a sub-frame are assigned with respect to a VSB frame in atime region;

FIG. 5 illustrates an alignment of data after being data interleaved andidentified;

FIG. 6 illustrates an enlarged portion of the data group shown in FIG. 5for a better understanding of the present invention;

FIG. 7 illustrates an alignment of data before being data interleavedand identified;

FIG. 8 illustrates an enlarged portion of the data group shown in FIG. 7for a better understanding of the present invention;

FIG. 9 illustrates an exemplary assignment order of data groups beingassigned to one of 5 sub-frames according to the present invention;

FIG. 10 illustrates an example of assigning a single parade to an M/Hframe according to the present invention;

FIG. 11 illustrates an example of RS frame payload according to thepresent invention;

FIG. 12 is a diagram illustrating a structure of an M/H header within anM/H service data packet according to the present invention;

FIG. 13(a) and FIG. 13(b) are diagrams illustrating another example ofRS frame payload according to the present invention; and

FIG. 14 illustrates a block diagram showing an embodiment of atransmitter according to the present invention;

FIG. 15 illustrates a block diagram showing an example of apre-processor according to the present invention;

FIG. 16 illustrates a conceptual block diagram of the M/H frame encoderaccording to the present invention;

FIG. 17 illustrates a detailed block diagram of an RS frame encoderaccording to the present invention;

FIG. 18(a) and FIG. 18(b) illustrate a process of one or two RS framebeing divided into several portions, based upon an RS frame mode value,and a process of each portion being assigned to a corresponding regionwithin the respective data group;

FIG. 19(a) to FIG. 19(c) illustrate error correction encoding and errordetection encoding processes according to an embodiment of the presentinvention;

FIG. 20(a) and FIG. 20(b) illustrate an example which a paradeconfigures of two RS frames

FIG. 21(a) and FIG. 21(b) illustrate an exemplary process of dividing anRS frame for configuring a data group according to the presentinvention;

FIG. 22 illustrates a block diagram of a block processor according to anembodiment of the present invention;

FIG. 23 illustrates a detailed block diagram of a convolution encoder ofthe block processor;

FIG. 24 illustrates a symbol interleaver of the block processor;

FIG. 25 illustrates a block diagram of a group formatter according to anembodiment of the present invention;

FIG. 26 illustrates a block diagram of a trellis encoder according to anembodiment of the present invention;

FIG. 27 illustrates an example of assignment of training sequenceswithin a data group before trellis encoding according to the presentinvention;

FIG. 28 illustrates an example of assignment of training sequenceswithin a data group after trellis encoding according to the presentinvention;

FIG. 29 illustrates an example of assigning signaling information areaaccording to an embodiment of the present invention;

FIG. 30 illustrates a detailed block diagram of a signaling encoderaccording to the present invention;

FIG. 31 illustrates an example of a syntax structure of TPC dataaccording to the present invention;

FIG. 32 illustrates an example of a transmission scenario of the TPCdata and the FIC data level according to the present invention;

FIG. 33 illustrates a syntax structure of an FIC chunk according to anembodiment of the present invention;

FIG. 34 illustrates a syntax structure of an FIC chunk header accordingto an embodiment of the present invention;

FIG. 35 illustrates a syntax structure of an FIC chunk payload accordingto an embodiment of the present invention;

FIG. 36 illustrates a syntax structure of an FIC segment headeraccording to an embodiment of the present invention;

FIG. 37 illustrates a syntax structure of a service map table (SMT)according to an embodiment of the present invention;

FIG. 38 illustrates a bitstream syntax structure ofcomponent_descriptor( ) according to an embodiment of the presentinvention;

FIG. 39 illustrates a syntax structure of an FIC segment headeraccording to an embodiment of the present invention;

FIG. 40 illustrates a syntax structure of an FIC segment headeraccording to another embodiment of the present invention;

FIG. 41 illustrates a table showing meaning of values of a wake-upindicator field according to an embodiment of the present invention;

FIG. 42 illustrates a syntax structure of an FIC chunk payload accordingto another embodiment of the present invention;

FIG. 43 illustrates a syntax structure of an EAS message descriptoraccording to an embodiment of the present invention;

FIG. 44 illustrates a syntax structure of an EAS message descriptoraccording to another embodiment of the present invention;

FIG. 45 illustrates an example of signaling an EAS message descriptor toensemble level according to an embodiment of the present invention;

FIG. 46 illustrates an example of signaling an EAS message descriptor toservice level according to an embodiment of the present invention;

FIG. 47 illustrates an example of displaying an emergency alert messageon a portion of screen according to an embodiment of the presentinvention;

FIG. 48 illustrates an example of displaying additional informationrelated to an emergency alert message on another portion of screenaccording to an embodiment of the present invention;

FIG. 49 illustrates a syntax structure of capabilities descriptoraccording to the present invention;

FIG. 50 illustrates a syntax structure of NRT service descriptoraccording to the present invention;

FIG. 51 illustrates a table showing meaning of values of a consumptionmodel field according to an embodiment of the present invention;

FIG. 52 illustrates a flow chart for receiving and displaying disasterinformation and disaster related-additional information by a broadcastreceiver according to an embodiment of the present invention;

FIG. 53 illustrates a flow chart for receiving and displaying disasterinformation and disaster related-additional information by a broadcastreceiver according to another embodiment of the present invention;

FIG. 54 illustrates an example of encapsulating an emergency alertmessage to IP datagram according to the present invention;

FIG. 55 illustrates an example of a syntax structure of emergency alertsystem descriptor capable of transmitting in a payload of IP datagram ofFIG. 54;

FIG. 56 illustrates a table showing meaning of values of a servicecategory field of SMT according to an embodiment of the presentinvention;

FIG. 57 illustrates an example of a bitstream syntax structure ofcomponent_data( ) providing signaling information for emergency alertmessage according to an embodiment of the present invention;

FIG. 58 illustrates an example of a bitstream syntax structure of EATsection according to an embodiment of the present invention;

FIG. 59 illustrates a flow chart for receiving and displaying disasterinformation and disaster related-additional information by a broadcastreceiver according to another embodiment of the present invention; and

FIG. 60 illustrates a block diagram of a receiving system according toan embodiment of the present invention.

BEST MODE

Reference will now be made in detail to the preferred embodiments of thepresent invention, examples of which are illustrated in the accompanyingdrawings. Wherever possible, the same reference numbers will be usedthroughout the drawings to refer to the same or like parts.

DEFINITION OF TERMS USED IN THE PRESENT INVENTION

In addition, although the terms used in the present invention areselected from generally known and used terms, some of the termsmentioned in the description of the present invention have been selectedby the applicant at his or her discretion, the detailed meanings ofwhich are described in relevant parts of the description herein.Furthermore, it is required that the present invention is understood,not simply by the actual terms used but by the meaning of each termlying within.

Among the terms used in the description of the present invention, mainservice data correspond to data that can be received by a fixedreceiving system and may include audio/video (A/V) data. Morespecifically, the main service data may include A/V data of highdefinition (HD) or standard definition (SD) levels and may also includediverse data types required for data broadcasting. Also, the known datacorrespond to data pre-known in accordance with a pre-arranged agreementbetween the receiving system and the transmitting system.

Additionally, among the terms used in the present invention, “M/H (orMH)” corresponds to the initials of “mobile” and “handheld” andrepresents the opposite concept of a fixed-type system. Furthermore, theM/H service data may include at least one of mobile service data andhandheld service data, and will also be referred to as “mobile servicedata” for simplicity. Herein, the mobile service data not onlycorrespond to M/H service data but may also include any type of servicedata with mobile or portable characteristics. Therefore, the mobileservice data according to the present invention are not limited only tothe M/H service data.

The above-described mobile service data may correspond to data havinginformation, such as program execution files, stock information, and soon, and may also correspond to A/V data. Most particularly, the mobileservice data may correspond to A/V data having lower resolution andlower data rate as compared to the main service data. For example, if anA/V codec that is used for a conventional main service corresponds to aMPEG-2 codec, a MPEG-4 advanced video coding (AVC) or scalable videocoding (SVC) having better image compression efficiency may be used asthe A/V codec for the mobile service. Furthermore, any type of data maybe transmitted as the mobile service data. For example, transportprotocol expert group (TPEG) data for broadcasting real-timetransportation information may be transmitted as the main service data.

Also, a data service using the mobile service data may include weatherforecast services, traffic information services, stock informationservices, viewer participation quiz programs, real-time polls andsurveys, interactive education broadcast programs, gaming services,services providing information on synopsis, character, background music,and filming sites of soap operas or series, services providinginformation on past match scores and player profiles and achievements,and services providing information on product information and programsclassified by service, medium, time, and theme enabling purchase ordersto be processed. Herein, the present invention is not limited only tothe services mentioned above.

In the present invention, the transmitting system provides backwardcompatibility in the main service data so as to be received by theconventional receiving system. Herein, the main service data and themobile service data are multiplexed to the same physical channel andthen transmitted.

Furthermore, the transmitting system according to the present inventionperforms additional encoding on the mobile service data and inserts thedata already known by the receiving system and transmitting system(e.g., known data), thereby transmitting the processed data.

Therefore, when using the transmitting system according to the presentinvention, the receiving system may receive the mobile service dataduring a mobile state and may also receive the mobile service data withstability despite various distortion and noise occurring within thechannel.

M/H Frame Structure

In the embodiment of the present invention, the mobile service data arefirst multiplexed with main service data in M/H frame units and, then,modulated in a VSB mode and transmitted to the receiving system.

At this point, one M/H frame configures of K1 number of sub-frames,wherein one sub-frame includes K2 number of slots. Also, each slot maybe configured of K3 number of data packets. In the embodiment of thepresent invention, K1 will be set to 5, K2 will be set to 16, and K3will be set to 156 (i.e., K1=5, K2=16, and K3=156). The values for K1,K2, and K3 presented in this embodiment either correspond to valuesaccording to a preferred embodiment or are merely exemplary. Therefore,the above-mentioned values will not limit the scope of the presentinvention.

FIG. 1 illustrates a structure of an M/H frame for transmitting andreceiving mobile service data according to the present invention. In theexample shown in FIG. 1, one M/H frame consists of 5 sub-frames, whereineach sub-frame includes 16 slots. In this case, the M/H frame accordingto the present invention includes 5 sub-frames and 80 slots.

Also, in a packet level, one slot is configured of 156 data packets(i.e., transport stream packets), and in a symbol level, one slot isconfigured of 156 data segments. Herein, the size of one slotcorresponds to one half (½) of a VSB field. More specifically, since one207-byte data packet has the same amount of data as a data segment, adata packet prior to being interleaved may also be used as a datasegment.

At this point, two VSB fields are grouped to form a VSB frame.

FIG. 2 illustrates an exemplary structure of a VSB frame, wherein oneVSB frame consists of 2 VSB fields (i.e., an odd field and an evenfield). Herein, each VSB field includes a field synchronization segmentand 312 data segments.

The slot corresponds to a basic time period for multiplexing the mobileservice data and the main service data. Herein, one slot may eitherinclude the mobile service data or be configured only of the mainservice data.

If one M/H frame is transmitted during one slot, the first 118 datapackets within the slot correspond to a data group. And, the remaining38 data packets become the main service data packets. In anotherexample, when no data group exists in a slot, the corresponding slot isconfigured of 156 main service data packets.

Meanwhile, when the slots are assigned to a VSB frame, an offset existsfor each assigned position.

FIG. 3 illustrates a mapping example of the positions to which the first4 slots of a sub-frame are assigned with respect to a VSB frame in aspace region. And, FIG. 4 illustrates a mapping example of the positionsto which the first 4 slots of a sub-frame are assigned with respect to aVSB frame in a time region.

Referring to FIG. 3 and FIG. 4, a 38^(th) data packet (TS packet #37) ofa 1^(st) slot (Slot #0) is mapped to the 1^(st) data packet of an oddVSB field. A 38^(th) data packet (TS packet #37) of a 2^(nd) slot (Slot#1) is mapped to the 157^(th) data packet of an odd VSB field. Also, a38^(th) data packet (TS packet #37) of a 3^(rd) slot (Slot #2) is mappedto the 1^(st) data packet of an even VSB field. And, a 38^(th) datapacket (TS packet #37) of a 4^(th) slot (Slot #3) is mapped to the157^(th) data packet of an even VSB field. Similarly, the remaining 12slots within the corresponding sub-frame are mapped in the subsequentVSB frames using the same method.

Meanwhile, one data group may be divided into at least one or morehierarchical regions. And, depending upon the characteristics of eachhierarchical region, the type of mobile service data being inserted ineach region may vary. For example, the data group within each region maybe divided (or categorized) based upon the receiving performance.

In an example given in the present invention, a data group is dividedinto regions A, B, C, and D in a data configuration after datainterleaving.

FIG. 5 illustrates an alignment of data after being data interleaved andidentified. FIG. 6 illustrates an enlarged portion of the data groupshown in FIG. 5 for a better understanding of the present invention.FIG. 7 illustrates an alignment of data before being data interleavedand identified. And, FIG. 8 illustrates an enlarged portion of the datagroup shown in FIG. 7 for a better understanding of the presentinvention. More specifically, a data structure identical to that shownin FIG. 5 is transmitted to a receiving system. In other words, one datapacket is data-interleaved so as to be scattered to a plurality of datasegments, thereby being transmitted to the receiving system.

FIG. 5 illustrates an example of one data group being scattered to 170data segments. At this point, since one 207-byte packet has the sameamount of data as one data segment, the packet that is not yet processedwith data-interleaving may be used as the data segment.

FIG. 5 shows an example of dividing a data group prior to beingdata-interleaved into 10 M/H blocks (i.e., M/H block 1 (B1) to M/H block10 (B10)). In this example, each M/H block has the length of 16segments. Referring to FIG. 5, only the RS parity data are allocated toa portion of 5 segments before the M/H block 1 (B1) and 5 segmentsbehind the M/H block 10 (B10). The RS parity data are excluded inregions A to D of the data group.

More specifically, when it is assumed that one data group is dividedinto regions A, B, C, and D, each M/H block may be included in any oneof region A to region D depending upon the characteristic of each M/Hblock within the data group. At this point, according to an embodimentof the present invention, each M/H block may be included in any one ofregion A to region D based upon an interference level of main servicedata.

Herein, the data group is divided into a plurality of regions to be usedfor different purposes. More specifically, a region of the main servicedata having no interference or a very low interference level may beconsidered to have a more resistant (or stronger) receiving performanceas compared to regions having higher interference levels. Additionally,when using a system inserting and transmitting known data in the datagroup, wherein the known data are known based upon an agreement betweenthe transmitting system and the receiving system, and when consecutivelylong known data are to be periodically inserted in the mobile servicedata, the known data having a predetermined length may be periodicallyinserted in the region having no interference from the main service data(i.e., a region wherein the main service data are not mixed). However,due to interference from the main service data, it is difficult toperiodically insert known data and also to insert consecutively longknown data to a region having interference from the main service data.

Referring to FIG. 5, M/H block 4 (B4) to M/H block 7 (B7) correspond toregions without interference of the main service data. M/H block 4 (B4)to M/H block 7 (B7) within the data group shown in FIG. 5 correspond toa region where no interference from the main service data occurs. Inthis example, a long known data sequence is inserted at both thebeginning and end of each M/H block. In the description of the presentinvention, the region including M/H block 4 (B4) to M/H block 7 (B7)will be referred to as “region A (=B4+B5+B6+B7)”. As described above,when the data group includes region A having a long known data sequenceinserted at both the beginning and end of each M/H block, the receivingsystem is capable of performing equalization by using the channelinformation that can be obtained from the known data. Therefore, thestrongest equalizing performance may be yielded (or obtained) from oneof region A to region D.

In the example of the data group shown in FIG. 5, M/H block 3 (B3) andM/H block 8 (B8) correspond to a region having little interference fromthe main service data. Herein, a long known data sequence is inserted inonly one side of each M/H block B3 and B8. More specifically, due to theinterference from the main service data, a long known data sequence isinserted at the end of M/H block 3 (B3), and another long known datasequence is inserted at the beginning of M/H block 8 (B8). In thepresent invention, the region including M/H block 3 (B3) and M/H block 8(B8) will be referred to as “region B(=B3+B8)”. As described above, whenthe data group includes region B having a long known data sequenceinserted at only one side (beginning or end) of each M/H block, thereceiving system is capable of performing equalization by using thechannel information that can be obtained from the known data. Therefore,a stronger equalizing performance as compared to region C/D may beyielded (or obtained).

Referring to FIG. 5, M/H block 2 (B2) and M/H block 9 (B9) correspond toa region having more interference from the main service data as comparedto region B. A long known data sequence cannot be inserted in any sideof M/H block 2 (B2) and M/H block 9 (B9). Herein, the region includingM/H block 2 (B2) and M/H block 9 (B9) will be referred to as “regionC(=B2+B9)”. Finally, in the example shown in FIG. 5, M/H block 1 (B1)and M/H block 10 (B10) correspond to a region having more interferencefrom the main service data as compared to region C. Similarly, a longknown data sequence cannot be inserted in any side of M/H block 1 (B1)and M/H block 10 (B10).

Herein, the region including M/H block 1 (B1) and M/H block 10 (B10)will be referred to as “region D (=B1+B10)”. Since region C/D is spacedfurther apart from the known data sequence, when the channel environmentundergoes frequent and abrupt changes, the receiving performance ofregion C/D may be deteriorated.

FIG. 7 illustrates a data structure prior to data interleaving. Morespecifically, FIG. 7 illustrates an example of 118 data packets beingallocated to a data group. FIG. 7 shows an example of a data groupconsisting of 118 data packets, wherein, based upon a reference packet(e.g., a 1^(st) packet (or data segment) or 157^(th) packet (or datasegment) after a field synchronization signal), when allocating datapackets to a VSB frame, 37 packets are included before the referencepacket and 81 packets (including the reference packet) are includedafterwards.

In other words, with reference to FIG. 5, a field synchronization signalis placed (or assigned) between M/H block 2 (B2) and M/H block 3 (B3).Accordingly, this indicates that the slot has an off-set of 37 datapackets with respect to the corresponding VSB field.

The size of the data groups, number of hierarchical regions within thedata group, the size of each region, the number of M/H blocks includedin each region, the size of each M/H block, and so on described aboveare merely exemplary. Therefore, the present invention will not belimited to the examples described above.

FIG. 9 illustrates an exemplary assignment order of data groups beingassigned to one of 5 sub-frames, wherein the 5 sub-frames configure anM/H frame. For example, the method of assigning data groups may beidentically applied to all M/H frames or differently applied to each M/Hframe. Furthermore, the method of assigning data groups may beidentically applied to all sub-frames or differently applied to eachsub-frame. At this point, when it is assumed that the data groups areassigned using the same method in all sub-frames of the correspondingM/H frame, the total number of data groups being assigned to an M/Hframe is equal to a multiple of ‘5’.

According to the embodiment of the present invention, a plurality ofconsecutive data groups is assigned to be spaced as far apart from oneanother as possible within the M/H frame. Thus, the system can becapable of responding promptly and effectively to any burst error thatmay occur within a sub-frame.

For example, when it is assumed that 3 data groups are assigned to asub-frame, the data groups are assigned to a 1^(st) slot (Slot #0), a5^(th) slot (Slot #4), and a 9^(th) slot (Slot #8) in the sub-frame,respectively. FIG. 9 illustrates an example of assigning 16 data groupsin one sub-frame using the above-described pattern (or rule). In otherwords, each data group is serially assigned to 16 slots corresponding tothe following numbers: 0, 8, 4, 12, 1, 9, 5, 13, 2, 10, 6, 14, 3, 11, 7,and 15.

Equation 1 below shows the above-described rule (or pattern) forassigning data groups in a sub-frame.j=(4i+0)mod 16  Equation 1

-   -   0=0 if i<4,    -   0=2 else if i<8,    -   Herein,    -   0=1 else if i<12,    -   0=3 else

Herein, j indicates the slot number within a sub-frame. The value of jmay range from 0 to 15 (i.e., 0≦j≦15). Also, value of i indicates thedata group number. The value of i may range from 0 to 15 (i.e., 0≦i≦15).

In the present invention, a collection of data groups included in an M/Hframe will be referred to as a “parade”. Based upon the RS frame mode,the parade transmits data of one or two RS frames.

The mobile service data within one RS frame may be assigned (or mapped)either to all of regions A/B/C/D within the corresponding data group, orto at least one of regions A/B/C/D. In the embodiment of the presentinvention, the mobile service data within one RS frame may be assigned(or mapped) either to all of regions A/B/C/D, or to at least one ofregions A/B and regions C/D. If the mobile service data are assigned tothe latter case (i.e., one of regions A/B and regions C/D), the RS framebeing assigned to regions A/B and the RS frame being assigned to regionsC/D within the corresponding data group are different from one another.In the description of the present invention, the RS frame being assignedto regions A/B within the corresponding data group will be referred toas a “primary RS frame”, and the RS frame being assigned to regions C/Dwithin the corresponding data group will be referred to as a “secondaryRS frame”, for simplicity. Also, the primary RS frame and the secondaryRS frame form (or configure) one parade. More specifically, when themobile service data within one RS frame are assigned either to all ofregions A/B/C/D within the corresponding data group, one paradetransmits one RS frame. In this case, also the RS frame will be referredto as a “primary RS frame”. Conversely, when the mobile service datawithin one RS frame are assigned either to at least one of regions A/Band regions C/D, one parade may transmit up to 2 RS frames.

More specifically, the RS frame mode indicates whether a paradetransmits one RS frame, or whether the parade transmits two RS frames.

Table 1 below shows an example of the RS frame mode.

TABLE 1 RS frame mode (2 bits) Description 00 There is only one primaryRS frame for all group regions 01 There are two separate RS frames.Primary RS frame for group regions A and B Secondary RS frame for groupregions C and D 10 Reserved 11 Reserved

Table 1 illustrates an example of allocating 2 bits in order to indicatethe RS frame mode. For example, referring to Table 1, when the RS framemode value is equal to ‘00’, this indicates that one parade transmitsone RS frame. And, when the RS frame mode value is equal to ‘01’, thisindicates that one parade transmits two RS frames, i.e., the primary RSframe and the secondary RS frame. More specifically, when the RS framemode value is equal to ‘01’, data of the primary RS frame for regionsA/B are assigned and transmitted to regions A/B of the correspondingdata group. Similarly, data of the secondary RS frame for regions C/Dare assigned and transmitted to regions C/D of the corresponding datagroup.

As described in the assignment of data groups, the parades are alsoassigned to be spaced as far apart from one another as possible withinthe sub-frame. Thus, the system can be capable of responding promptlyand effectively to any burst error that may occur within a sub-frame.

Furthermore, the method of assigning parades may be identically appliedto all sub-frames or differently applied to each sub-frame. According tothe embodiment of the present invention, the parades may be assigneddifferently for each M/H frame and identically for all sub-frames withinan M/H frame. More specifically, the M/H frame structure may vary by M/Hframe units. Thus, an ensemble rate may be adjusted on a more frequentand flexible basis.

FIG. 10 illustrates an example of multiple data groups of a singleparade being assigned (or allocated) to an M/H frame.

More specifically, FIG. 10 illustrates an example of a plurality of datagroups included in a single parade, wherein the number of data groupsincluded in a sub-frame is equal to ‘3’, being allocated to an M/Hframe. Referring to FIG. 10, 3 data groups are sequentially assigned toa sub-frame at a cycle period of 4 slots. Accordingly, when this processis equally performed in the 5 sub-frames included in the correspondingM/H frame, 15 data groups are assigned to a single M/H frame. Herein,the 15 data groups correspond to data groups included in a parade.Therefore, since one sub-frame is configured of 4 VSB frame, and since 3data groups are included in a sub-frame, the data group of thecorresponding parade is not assigned to one of the 4 VSB frames within asub-frame.

For example, when it is assumed that one parade transmits one RS frame,and that a RS frame encoder located in a later block performsRS-encoding on a payload of the corresponding RS frame, thereby adding24 bytes of parity data to the corresponding RS frame payload andtransmitting the processed RS frame, the parity data occupyapproximately 11.37% (=24/(187+24)×100) of the total code word length.Meanwhile, when one sub-frame includes 3 data groups, and when the datagroups included in the parade are assigned, as shown in FIG. 10, a totalof 15 data groups form an RS frame. Accordingly, even when an erroroccurs in an entire data group due to a burst noise within a channel,the percentile is merely 6.67% (=1/15×100). Therefore, the receivingsystem may correct all errors by performing an erasure RS decodingprocess. More specifically, when the erasure RS decoding is performed, anumber of channel errors corresponding to the number of RS parity bytesmay be corrected. By doing so, the receiving system may correct theerror of at least one data group within one parade. Thus, the minimumburst noise length correctable by a RS frame is over 1 VSB frame.

Meanwhile, when data groups belonging to a parade are assigned as shownin FIG. 10, either main service data may be assigned between each datagroup, or data groups corresponding to different parades may be assignedbetween each data group. More specifically, data groups corresponding tomultiple parades may be assigned to one M/H frame.

Basically, the method of assigning data groups corresponding to multipleparades is very similar to the method of assigning data groupscorresponding to a single parade. In other words, data groups includedin other parades that are to be assigned to an M/H frame are alsorespectively assigned according to a cycle period of 4 slots.

At this point, data groups of a different parade may be sequentiallyassigned to the respective slots in a circular method. Herein, the datagroups are assigned to slots starting from the ones to which data groupsof the previous parade have not yet been assigned.

For example, when it is assumed that data groups corresponding to aparade are assigned as shown in FIG. 10, data groups corresponding tothe next parade may be assigned to a sub-frame starting either from the12^(th) slot of a sub-frame. However, this is merely exemplary. Inanother example, the data groups of the next parade may also besequentially assigned to a different slot within a sub-frame at a cycleperiod of 4 slots starting from the 3^(rd) slot.

As described above, data groups of multiple parades may be assigned to asingle M/H frame, and, in each sub-frame, the data groups are seriallyallocated to a group space having 4 slots from left to right.

Therefore, a number of groups of one parade per sub-frame (NOG) maycorrespond to any one integer from ‘1’ to ‘8’. Herein, since one M/Hframe includes 5 sub-frames, the total number of data groups within aparade that can be allocated to an M/H frame may correspond to any onemultiple of ‘5’ ranging from ‘5’ to ‘40’.

As described above, an M/H frame is divided into 5 sub-frames. Datagroups corresponding to a plurality of parades co-exist in eachsub-frame. Herein, the data groups corresponding to each parade aregrouped by M/H frame units, thereby configuring a single parade.

Meanwhile, an RS frame according to the present invention includes an RSframe payload, RS parity data added at bottom of each column of the RSframe payload, and CRC data added at left end of each row of the RSframe payload having the RS parity data.

The RS frame payload has the size of N (row)×187 (column), as shown inFIG. 11. Herein, N represents the length of a row (i.e., number ofcolumns), and 187 corresponds to the length of a column (i.e., number ofrows.

In the present invention, for convenience of description, each row ofthe N bytes will be referred to as M/H service data packet (or M/H TPpacket).

Each M/H service data packet within the RS frame payload includes M/Hheader (or MH TP header) of 2 bytes, a stuffing region of k bytes, andM/H payload of N-2-k bytes as shown in FIG. 12. At this time, k has avalue of 0 or a value greater than 0. The M/H payload includes IPdatagrams of signaling table information and/or mobile service dataaccording to an embodiment of the present invention. In this case, theM/H header of 2 bytes is only one example, and corresponding bytes canbe varied depending on a designer. Accordingly, the present inventionwill not be limited to such example.

At this time, as the M/H service data packet includes M/H header, theM/H header may not reach N bytes.

In this case, stuffing bytes can be assigned to the remaining payloadpart of the corresponding M/H service data packet. For example, afterprogram table information is assigned to one M/H service data packet, ifthe length of the M/H service data packet is N-20 bytes including theM/H header, the stuffing bytes can be assigned to the remaining 20bytes. In this case, the value k becomes 20, and the M/H payload regionwithin the corresponding M/H service data packet includes N-2-20 bytes.

The RS frame payload is generated by collecting signaling tableinformation corresponding to one or more mobile services and/or IPdatagram of the mobile service data. For example, signaling tableinformation for two kinds of mobile services called news (for example,IP datagram for mobile service 1) and the stocks (for example, IPdatagram for mobile service 2) and IP datagram of mobile service datacan be included in one RS frame payload.

More specifically, in the transmitting system (e.g., mobile broadcaststation), the mobile service data (e.g., A/V steaming) are packetizedbased upon a real time protocol (RTP) method. The RTP packet is thenpacketized once again based upon a user datagram protocol (UDP) method.Thereafter, the RTP/UDP packet is in turn packetized based upon an IPmethod, thereby being packetized into RTP/UDP/IP packet data. In thedescription of the present invention, the packetized RTP/UDP/IP packetdata will be referred to as an IP datagram for simplicity.

Furthermore, service information for receiving mobile services may beprovided in the form of a signaling table. And, a service signalingchannel transmitting such signaling table is packetized based upon a UDPmethod. And, the packetized UDP data are then packetized based upon anIP method, thereby being packetized into UDP/IP data. In the descriptionof the present invention, the packetized UDP/IP packet data will also bereferred to as an IP datagram for simplicity. According to an embodimentof the present invention, the service signaling channel is encapsulatedinto an IP datagram having a well-known destination IP address and awell-known destination UDP port number.

More specifically, one RS frame payload includes an IP datagram ofmobile service data for at least one or more mobile services.Furthermore, the RS frame payload includes an IP datagram of a servicesignaling channel for receiving the mobile service data.

According to the embodiment of the present invention, among a servicemap table (SMT), a guide access table (GAT), a cell information table(CIT), a service labeling table (SLT), and a rating region table (RRT),the present invention transmits at least one signaling table through theservice signaling channel. Herein, the signaling tables presented in theembodiment of the present invention are merely examples for facilitatingthe understanding of the present invention. Therefore, the presentinvention is not limited only to the exemplary signaling tables that canbe transmitted through the service signaling channel.

The SMT provides signaling information on ensemble levels. Also, eachSMT provides IP access information for each mobile service belonging tothe corresponding ensemble including each SMT. Furthermore, the SMTprovides IP stream component level information required for thecorresponding mobile service. The RRT transmits information on regionand consultation organs for program ratings. More specifically, the RRTprovides content advisory rating information. The GAT providesinformation on SG providers, which transmit the service guides. Also,the GAT provides service guide bootstrapping information required foraccessing the SG. The CIT provides channel information of each cell,which corresponds to the frequency domain of a broadcast signal. Herein,a cell refers to a scope affected (or influenced) by a transmitter basedupon a physical frequency in a multi-frequency network (MFN) environment(or condition). More specifically, the CIT provides information on acarrier wave frequency of an adjacent cell in the current transmitter(or transmitting system). Therefore, based upon the CIT information, areceiver (or receiving system) can travel from one transmitter's (orexciter's) coverage area to another. The SLT provides minimum requiredinformation for an exclusive usage of a channel scan process. Morespecifically, according to the embodiment of the present invention,other than the SMT, by using the SLT for the exclusive usage of thechannel scan process, so as to configure a set of minimum informationfor the channel scan process, the channel scanning speed may beincreased.

According to an embodiment of the present invention, each signalingtable is divided into at least one section. Then, each section isencapsulated to a UDP/IP header, thereby being transmitted through theservice signaling channel. In this case, the number of UDP/IP packetsbeing transmitted through the service signaling channel may vary basedupon the number of signaling tables being transmitted through theservice signaling channel and the number of sections in each signalingtable.

At this point, all UDP/IP packets transmitted through the servicesignaling channel have the same number of well-known target IP addressesand well-known target UDP port numbers. For example, when it is assumedthat the SMT, RRT, and GAT are transmitted through the service signalingchannel, the target IP address and target UDP port number of all UDP/IPpackets transmitting the SMT, RRT, and GAT are identical to one another.Furthermore, the target IP address and the target UDP port numberrespectively correspond to well-known values, i.e., values pre-known bythe receiving system based upon an agreement between the receivingsystem and the transmitting system.

Therefore, the identification of each signaling table included in theservice signaling data is performed by a table identifier. The tableidentifier may correspond to a table_id field existing in thecorresponding signaling table or in the header of the correspondingsignaling table section. And, when required, identification may beperformed by further referring to a table_id_extension field.

FIG. 12 is a diagram illustrating examples of fields allocated to theM/H header region within the M/H service data packet according to thepresent invention. Examples of the fields include type_indicator field,error_indicator field, stuff_indicator field, and pointer field.

The type_indicator field can allocate 3 bits, for example, andrepresents a type of data allocated to payload within the correspondingM/H service data packet. In other words, the type_indicator fieldindicates whether data of the payload is IP datagram or program tableinformation. At this time, each data type constitutes one logicalchannel. In the logical channel which transmits the IP datagram, severalmobile services are multiplexed and then transmitted. Each mobileservice undergoes demultiplexing in the IP layer.

The error_indicator field can allocate 1 bit, for example, andrepresents whether the corresponding M/H service data packet has anerror. For example, if the error_indicator field has a value of 0, itmeans that there is no error in the corresponding M/H service datapacket. If the error_indicator field has a value of 1, it means thatthere may be an error in the corresponding M/H service data packet.According to an embodiment of the present invention, a value of zero areindicated and transmitted on all error_indicator fields within the RSframe.

The stuff_indicator field can allocate 1 bit, for example, andrepresents whether stuffing byte exists in payload of the correspondingM/H service data packet. For example, if the stuff_indicator field has avalue of 0, it means that there is no stuffing byte in the correspondingM/H service data packet. If the stuff_indicator field has a value of 1,it means that stuffing byte exists in the corresponding M/H service datapacket.

The pointer field can allocate 11 bits, for example, and representsposition information where new data (i.e., new signaling information ornew IP datagram) starts in the corresponding M/H service data packet.

For example, if IP datagram for mobile service 1 and IP datagram formobile service 2 are allocated to the first M/H service data packetwithin the RS frame payload as illustrated in FIG. 11, the pointer fieldvalue represents the start position of the IP datagram for mobileservice 2 within the M/H service data packet.

Also, if there is no new data in the corresponding M/H service datapacket, the corresponding field value is expressed as a maximum valueexemplarily. According to the embodiment of the present invention, since11 bits are allocated to the pointer field, if 2047 is expressed as thepointer field value, it means that there is no new data in the packet.The point where the pointer field value is 0 can be varied depending onthe type_indicator field value and the stuff_indicator field value.

It is to be understood that the order, the position, and the meaning ofthe fields allocated to the header within the M/H service data packetillustrated in FIG. 12 are exemplarily illustrated for understanding ofthe present invention. Since the order, the position and the meaning ofthe fields allocated to the header within the M/H service data packetand the number of additionally allocated fields can easily be modifiedby those skilled in the art, the present invention will not be limitedto the above example.

FIG. 13(a) and FIG. 13(b) illustrate another examples of RS framepayload according to the present invention. FIG. 13(a) illustrates anexample of primary RS frame payload to be allocated to regions A/Bwithin the data group, and FIG. 13(b) illustrates an example ofsecondary RS frame payload to be allocated to regions C/D within thedata group.

In FIG. 13(a) and FIG. 13(b), a column length (i.e., the number of rows)of the RS frame payload to be allocated to the regions A/B and a columnlength (i.e., the number of rows) of the RS frame payload to beallocated to the regions C/D are 187 equally. However, row lengths (i.e,the number of columns) may be different from each other.

According to the embodiment of the present invention, when the rowlength of the primary RS frame payload to be allocated to the regionsA/B within the data group is N1 bytes and the row length of thesecondary RS frame payload to be allocated to the regions C/D within thedata group is N2 bytes, a condition of N1>N2 is satisfied.

In this case, N1 and N2 can be varied depending on the transmissionparameter or a region of the data group, to which the corresponding RSframe payload will be transmitted.

For convenience of the description, each row of the N1 and N2 bytes willbe referred to as the M/H service data packet. In the present invention,the primary RS frame payload for the regions A/B within the data groupand the secondary RS frame payload for the regions C/D within the datagroup can include at least one of IP datagrams of signaling tableinformation and mobile service data. Also, one RS frame payload caninclude IP datagram corresponding to one or more mobile services.

Corresponding parts of FIG. 11 can be applied to the other parts, whichare not described in FIG. 13(a) and FIG. 13(b).

Meanwhile, the value of N, which corresponds to the number of columnswithin an RS frame payload, can be decided according to Equation 2.

$\begin{matrix}{N = {\left\lfloor \frac{5 \times {NoG} \times {PL}}{187 + P} \right\rfloor - 2}} & {{Equation}\mspace{14mu} 2}\end{matrix}$

Herein, NoG indicates the number of data groups assigned to a sub-frame.PL represents the number of SCCC payload data bytes assigned to a datagroup. And, P signifies the number of RS parity data bytes added to eachcolumn of the RS frame payload. Finally, └X┘ is the greatest integerthat is equal to or smaller than X.

More specifically, in Equation 2, PL corresponds to the length of an RSframe portion. The value of PL is equivalent to the number of SCCCpayload data bytes that are assigned to the corresponding data group.Herein, the value of PL may vary depending upon the RS frame mode, SCCCblock mode, and SCCC outer code mode. Table 2 to Table 5 belowrespectively show examples of PL values, which vary in accordance withthe RS frame mode, SCCC block mode, and SCCC outer code mode. The SCCCblock mode and the SCCC outer code mode will be described in detail in alater process.

TABLE 2 SCCC outer code mode for Region A for Region B for Region C forRegion D PL 00 00 00 00 9624 00 00 00 01 9372 00 00 01 00 8886 00 00 0101 8634 00 01 00 00 8403 00 01 00 01 8151 00 01 01 00 7665 00 01 01 017413 01 00 00 00 7023 01 00 00 01 6771 01 00 01 00 6285 01 00 01 01 603301 01 00 00 5802 01 01 00 01 5550 01 01 01 00 5064 01 01 01 01 4812Others Reserved

Table 2 shows an example of the PL values for each data group within anRS frame, wherein each PL value varies depending upon the SCCC outercode mode, when the RS frame mode value is equal to ‘00’, and when theSCCC block mode value is equal to ‘00’.

For example, when it is assumed that each SCCC outer code mode value ofregions A/B/C/D within the data group is equal to ‘00’ (i.e., the blockprocessor 302 of a later block performs encoding at a coding rate of1/2), the PL value within each data group of the corresponding RS framemay be equal to 9624 bytes. More specifically, 9624 bytes of mobileservice data within one RS frame may be assigned to regions A/B/C/D ofthe corresponding data group.

TABLE 3 SCCC outer code mode PL 00 9624 01 4812 Others Reserved

Table 3 shows an example of the PL values for each data group within anRS frame, wherein each PL value varies depending upon the SCCC outercode mode, when the RS frame mode value is equal to ‘00’, and when theSCCC block mode value is equal to ‘01’.

TABLE 4 SCCC outer code mode For Region A for Region B PL 00 00 7644 0001 6423 01 00 5043 01 01 3822 Others Reserved

Table 4 shows an example of the PL values for each data group within aprimary RS frame, wherein each PL value varies depending upon the SCCCouter code mode, when the RS frame mode value is equal to ‘01’, and whenthe SCCC block mode value is equal to ‘00’. For example, when each SCCCouter code mode value of regions A/B is equal to ‘00’, 7644 bytes ofmobile service data within a primary RS frame may be assigned to regionsA/B of the corresponding data group.

TABLE 5 SCCC outer code mode For Region C for Region D PL 00 00 1980 0001 1728 01 00 1242 01 01 990 Others Reserved

Table 5 shows an example of the PL values for each data group within asecondary RS frame, wherein each PL value varies depending upon the SCCCouter code mode, when the RS frame mode value is equal to ‘01’, and whenthe SCCC block mode value is equal to ‘00’. For example, when each SCCCouter code mode value of regions C/D is equal to ‘00’, 1980 bytes ofmobile service data within a secondary RS frame may be assigned toregions C/D of the corresponding data group.

Meanwhile, a predetermined portion of each data group (i.e., 37bytes/data group) is used for delivering (or sending) FIC information(i.e., one FIC segment), wherein the FIC information is separatelyencoded from the RS-encoding process on the mobile service data.

Also, the concept of an M/H ensemble is applied in the embodiment of thepresent invention, thereby defining a collection (or group) of services.Each M/H ensemble carries the same QoS and is coded with the same FECcode. Herein, the M/H ensemble is used as the same meaning of ensemble.Furthermore, each ensemble has a unique identifier (i.e., ensemble ID)and corresponds to consecutive RS frames.

A transmitting/receiving system according to an embodiment of thepresent invention operates (or manages) two data channels. One datachannel is an RS frame data channel for transmitting contents and theother data channel is an FIC (Fast Information Channel) for serviceacquisition. The present invention is intended that mapping (binding)information between an ensemble and a mobile service is signaled usingan FIC chunk and the FIC chunk is transmitted through the FIC by beingsegmented into an FIC segment unit, whereby the receiving system canperform fast service acquisition.

Transmitter

FIG. 14 illustrates a block diagram showing an example of thetransmitter according to an embodiment of the present invention. Herein,the transmitter includes a packet jitter mitigator 220, a pre-processor230, a packet multiplexer 240, a post-processor 250, a synchronization(sync) multiplexer 260, and a transmission unit 270.

At this point, main service data are inputted to the packet jittermitigator 220 and mobile service data are inputted to the pre-processor230 according to an embodiment of the present invention. Furthermore,main service data packets including main service data can be inputted tothe packet jitter mitigator 220 and mobile service data packetsincluding mobile service data can be inputted to the pre-processor 230according to another embodiment of the present invention.

The pre-processor 230 performs an additional encoding process of themobile service data inputted. The pre-processor 230 also performs aprocess of configuring a data group so that the data group may bepositioned at a specific place in accordance with the purpose of thedata, which are to be transmitted on a transmission frame. This is toenable the mobile service data to respond swiftly and strongly againstnoise and channel changes. FIG. 15 illustrates a block diagram showingthe structure of a pre-processor 230 according to the present invention.Herein, the pre-processor 230 includes an M/H frame encoder 301, a blockprocessor 302, a group formatter 303, a signaling encoder 304, and apacket formatter 305.

The M/H frame encoder 301, which is included in the pre-processor 230having the above-described structure, data-randomizes the mobile servicedata inputted, thereby forming at least one RS frame belonging to anensemble. The M/H frame encoder 301 may include at least one RS frameencoder. More specifically, RS frame encoders may be provided inparallel, wherein the number of RS frame encoders is equal to the numberof parades within the M/H frame. As described above, the M/H frame is abasic time cycle period for transmitting at least one parade. Also, eachparade consists of one or two RS frames.

FIG. 16 illustrates a conceptual block diagram of the M/H frame encoder301 according to an embodiment of the present invention. The M/H frameencoder 301 includes an input demultiplexer (DEMUX) 309, M number of RSframe encoders 310 to 31M-1, and an output multiplexer (MUX) 320.Herein, represent the number of parades included in one M/H frame.

The demultiplexer 309 output the inputted mobile service data packet toa corresponding RS frame encoder among M number of RS frame encoders inensemble units.

According to an embodiment of the present invention, each RS frameencoder forms an RS frame payload using mobile service data inputted andperforms at least one of an error correction encoding process and anerror detection encoding process in RS frame payload units, therebyforming an RS frame. Also, each RS frame encoder divides the RS frameinto a plurality of portions, in order to assign theerror-correction-encoded RS frame data to a plurality of data groups.Based upon the RS frame mode of Table 1, data within one RS frame may beassigned either to all of regions A/B/C/D within multiple data groups,or to at least one of regions A/B and regions C/D within multiple datagroups.

When the RS frame mode value is equal to ‘01’, i.e., when the data ofthe primary RS frame are assigned to regions A/B of the correspondingdata group and data of the secondary RS frame are assigned to regionsC/D of the corresponding data group, each RS frame encoder creates aprimary RS frame and a secondary RS frame for each parade. Conversely,when the RS frame mode value is equal to ‘00’, when the data of theprimary RS frame are assigned to all of regions A/B/C/D, each RS frameencoder creates a RS frame (i.e., a primary RS frame) for each parade.

Also, each RS frame encoder divides each RS frame into several portions.Each portion of the RS frame is equivalent to a data amount that can betransmitted by a data group. The output multiplexer (MUX) 320multiplexes portions within M number of RS frame encoders 310 to 310M-1are multiplexed and then outputted to the block processor 302.

For example, if one parade transmits two RS frames, portions of primaryRS frames within M number of RS frame encoders 310 to 310M-1 aremultiplexed and outputted. Thereafter, portions of secondary RS frameswithin M number of RS frame encoders 310 to 310M-1 are multiplexed andtransmitted.

FIG. 17 illustrates a detailed block diagram of an RS frame encoderamong a plurality of RS frame encoders within an M/H frame encoder.

One RS frame encoder may include a primary encoder 410 and a secondaryencoder 420. Herein, the secondary encoder 420 may or may not operatebased upon the RS frame mode. For example, when the RS frame mode valueis equal to ‘00’, as shown in Table 1, the secondary encoder 420 doesnot operate.

The primary encoder 410 may include a data randomizer 411, aReed-Solomon-cyclic redundancy check (RS-CRC) encoder (412), and a RSframe divider 413. And, the secondary encoder 420 may also include adata randomizer 421, a RS-CRC encoder (422), and a RS frame divider 423.

More specifically, the data randomizer 411 of the primary encoder 410receives mobile service data belonging to a primary ensemble outputtedfrom the output demultiplexer (DEMUX) 309. Then, after randomizing thereceived mobile service data, the data randomizer 411 outputs therandomized data to the RS-CRC encoder 412.

The RS-CRC encoder 412 performs FEC (Forward Error Correction) encodingon the randomized mobile service data using at least one of aReed-Solomon (RS) code and a cyclic redundancy check (CRC) code andoutputs to the RS frame divider 413.

The RS-CRC encoder 412 groups a plurality of mobile service data that israndomized and inputted, so as to form a RS frame payload. Then, theRS-CRC encoder 412 performs at least one of an error correction encodingprocess and an error detection encoding process in RS frame payloadunits, thereby forming an RS frame. Accordingly, robustness may beprovided to the mobile service data, thereby scattering group error thatmay occur during changes in a frequency environment, thereby enablingthe mobile service data to respond to the frequency environment, whichis extremely vulnerable and liable to frequent changes.

Also, the RS-CRC encoder 412 groups a plurality of RS frame so as tocreate a super frame, thereby performing a row permutation process insuper frame units. The row permutation process may also be referred toas a “row interleaving process”. Hereinafter, the process will bereferred to as “row permutation” for simplicity. In the presentinvention, the row permutation process is optional.

More specifically, when the RS-CRC encoder 412 performs the process ofpermuting each row of the super frame in accordance with apre-determined rule, the position of the rows within the super framebefore and after the row permutation process is changed. If the rowpermutation process is performed by super frame units, and even thoughthe section having a plurality of errors occurring therein becomes verylong, and even though the number of errors included in the RS frame,which is to be decoded, exceeds the extent of being able to becorrected, the errors become dispersed within the entire super frame.Thus, the decoding ability is even more enhanced as compared to a singleRS frame.

At this point, as an example of the present invention, RS-encoding isapplied for the error correction encoding process, and a cyclicredundancy check (CRC) encoding is applied for the error detectionprocess in the RS-CRC encoder 412. When performing the RS-encoding,parity data that are used for the error correction are generated. And,when performing the CRC encoding, CRC data that are used for the errordetection are generated.

The CRC data generated by CRC encoding may be used for indicatingwhether or not the mobile service data have been damaged by the errorswhile being transmitted through the channel. In the present invention, avariety of error detection coding methods other than the CRC encodingmethod may be used, or the error correction coding method may be used toenhance the overall error correction ability of the receiving system.

FIG. 18(a) and FIG. 18(b) illustrate a process of one or two RS framebeing divided into several portions, based upon an RS frame mode value,and a process of each portion being assigned to a corresponding regionwithin the respective data group. According to an embodiment of thepresent invention, the data assignment within the data group isperformed by the group formatter 303.

More specifically, FIG. 18(a) shows an example of the RS frame modevalue being equal to ‘00’. Herein, only the primary encoder 410 of FIG.17 operates, thereby forming one RS frame for one parade. Then, the RSframe is divided into several portions, and the data of each portion areassigned to regions A/B/C/D within the respective data group.

FIG. 18(b) shows an example of the RS frame mode value being equal to‘01’. Herein, both the primary encoder 410 and the secondary encoder 420of FIG. 17 operate, thereby forming two RS frames for one parade, i.e.,one primary RS frame and one secondary RS frame. Then, the primary RSframe is divided into several portions, and the secondary RS frame isdivided into several portions. At this point, the data of each portionof the primary RS frame are assigned to regions A/B within therespective data group. And, the data of each portion of the secondary RSframe are assigned to regions C/D within the respective data group.

Detailed Description of the RS Frame

FIG. 19(a) illustrates an example of an RS frame being generated fromthe RS-CRC encoder 412 according to the present invention.

When the RS frame payload is formed, as shown in FIG. 19(a), the RS-CRCencoder 412 performs a (Nc,Kc)-RS encoding process on each column, so asto generate Nc−Kc(=P) number of parity bytes. Then, the RS-CRC encoder412 adds the newly generated P number of parity bytes after the verylast byte of the corresponding column, thereby creating a column of(187+P) bytes.

Herein, as shown in FIG. 19(a), Kc is equal to 187 (i.e., Kc=187), andNc is equal to 187+P (i.e., Nc=187+P).

Herein, the value of P may vary depending upon the RS code mode. Table 6below shows an example of an RS code mode, as one of the RS encodinginformation.

TABLE 6 RS code Number of mode RS code Parity Bytes (P) 00 (211,187) 2401 (223,187) 36 10 (235,187) 48 11 Reserved Reserved

Table 6 shows an example of 2 bits being assigned in order to indicatethe RS code mode. The RS code mode represents the number of parity bytescorresponding to the RS frame payload.

For example, when the RS code mode value is equal to ‘10’,(235,187)-RS-encoding is performed on the RS frame payload of FIG.19(a), so as to generate 48 parity data bytes. Thereafter, the 48 paritybytes are added after the last data byte of the corresponding column,thereby creating a column of 235 data bytes.

When the RS frame mode value is equal to ‘00’ in Table 1 (i.e., when theRS frame mode indicates a single RS frame), only the RS code mode of thecorresponding RS frame is indicated. However, when the RS frame modevalue is equal to ‘01’ in Table 1 (i.e., when the RS frame modeindicates multiple RS frames), the RS code mode corresponding to aprimary RS frame and a secondary RS frame. More specifically, it ispreferable that the RS code mode is independently applied to the primaryRS frame and the secondary RS frame.

When such RS encoding process is performed on all N number of columns, asize of N(row)×(187+P)(column) bytes may be generated, as shown in FIG.19(b).

Each row of the RS frame payload is configured of N bytes. However,depending upon channel conditions between the transmitting system andthe receiving system, error may be included in the RS frame payload.When errors occur as described above, CRC data (or CRC code or CRCchecksum) may be used on each row unit in order to verify whether errorexists in each row unit.

The RS-CRC encoder 412 may perform CRC encoding on the mobile servicedata being RS encoded so as to create (or generate) the CRC data. TheCRC data being generated by CRC encoding may be used to indicate whetherthe mobile service data have been damaged while being transmittedthrough the channel.

The present invention may also use different error detection encodingmethods other than the CRC encoding method. Alternatively, the presentinvention may use the error correction encoding method to enhance theoverall error correction ability of the receiving system.

FIG. 19(c) illustrates an example of using a 2-byte (i.e., 16-bit) CRCchecksum as the CRC data. Herein, a 2-byte CRC checksum is generated forN number of bytes of each row, thereby adding the 2-byte CRC checksum atthe end of the N number of bytes. Thus, each row is expanded to (N+2)number of bytes.

Equation 3 below corresponds to an exemplary equation for generating a2-byte CRC checksum for each row being configured of N number of bytes.g(x)=x ¹⁶ +x ¹² +x ⁵+1  Equation 3

The process of adding a 2-byte checksum in each row is only exemplary.Therefore, the present invention is not limited only to the exampleproposed in the description set forth herein.

As described above, when the process of RS encoding and CRC encoding arecompleted, the (N×187)-byte RS frame payload is converted into a(N+2)×(187+P)-byte RS frame.

Based upon an error correction scenario of a RS frame formed asdescribed above, the data bytes within the RS frame are transmittedthrough a channel in a row direction. At this point, when a large numberof errors occur during a limited period of transmission time, errorsalso occur in a row direction within the RS frame being processed with adecoding process in the receiving system. However, in the perspective ofRS encoding performed in a column direction, the errors are shown asbeing scattered. Therefore, error correction may be performed moreeffectively. At this point, a method of increasing the number of paritydata bytes (P) may be used in order to perform a more intense errorcorrection process. However, using this method may lead to a decrease intransmission efficiency. Therefore, a mutually advantageous method isrequired. Furthermore, when performing the decoding process, an erasuredecoding process may be used to enhance the error correctionperformance.

The above description of the present invention corresponds to theprocesses of forming (or creating) and encoding an RS frame, when a datagroup is divided into regions A/B/C/D, and when data of an RS frame areassigned to all of regions A/B/C/D within a plurality of data groups.More specifically, the above description corresponds to an embodiment ofthe present invention, wherein one RS frame is transmitted using oneparade. In this embodiment, the secondary encoder 420 does not operate(or is not active).

Meanwhile, 2 RS frames are transmitting using one parade, the data ofthe primary RS frame may be assigned to regions A/B within the datagroups and be transmitted, and the data of the secondary RS frame may beassigned to regions C/D within the data groups and be transmitted. Atthis point, the primary encoder 410 receives the mobile service datathat are to be assigned to regions A/B within the data groups, forms theprimary RS frame payload, and then performs RS-encoding and CRC-encodingon the primary RS frame payload, thereby forming the primary RS frame.Similarly, the secondary encoder 420 receives the mobile service datathat are to be assigned to regions C/D within the data groups, forms thesecondary RS frame payload, and then performs RS-encoding andCRC-encoding on the secondary RS frame payload thereby forming thesecondary RS frame. More specifically, the primary RS frame and thesecondary RS frame are generated independently.

FIG. 20 illustrates examples of receiving the mobile service data thatare to be assigned to regions A/B within the data group, so as to formthe primary RS frame payload, and receives the mobile service data thatare to be assigned to regions C/D within the data group, so as to formthe secondary RS frame payload, thereby performing error correctionencoding and error detection encoding on each of the first and secondaryRS frame payloads.

More specifically, FIG. 20(a) illustrates an example of the RS-CRCencoder 412 of the primary encoder 410 receiving mobile service data ofthe primary ensemble that are to be assigned to regions A/B within thecorresponding data group, so as to create an RS frame payload having thesize of N1(row)×187(column). Then, in this example, the primary encoder410 performs RS-encoding on each column of the RS frame payload createdas described above, thereby adding P1 number of parity data bytes ineach column. Finally, the primary encoder 410 performs CRC-encoding oneach row, thereby adding a 2-byte checksum in each row, thereby formingan primary RS frame.

FIG. 20(b) illustrates an example of the RS-CRC encoder 422 of thesecondary encoder 420 receiving mobile service data of the secondaryensemble that are to be assigned to regions C/D within the correspondingdata group, so as to create an RS frame payload having the size ofN2(row)×187(column). Then, in this example, the secondary encoder 420performs RS-encoding on each column of the RS frame payload created asdescribed above, thereby adding P2 number of parity data bytes in eachcolumn. Finally, the secondary encoder 420 performs CRC-encoding on eachrow, thereby adding a 2-byte checksum in each row, thereby forming ansecondary RS frame.

At this point, each of the RS-CRC encoders 412 and 422 performs RS frameconfiguration, error correction encoding, error detection encoding byreferring to a transmission parameter, for example, at least one of M/Hframe information, FIC information, RS frame information (including RSframe mode information), RS encoding information (including RS code modeinformation), SCCC information (including SCCC block mode informationand SCCC outer code mode information). Furthermore, the transmissionparameters should also be transmitted to the receiving system so thatthe receiving system can perform a normal decoding process. At thispoint, as an example of the present invention, the transmissionparameter is transmitted through transmission parameter channel (TPC) toa receiving system. The TPC will be described in detail in a later.

The data of the primary RS frame, which is encoded by RS frame units bythe RS-CRC encoder 412 of the primary encoder 410, are outputted to theRS frame divider 413. If the secondary encoder 420 also operates in theembodiment of the present invention, the data of the secondary RS frame,which is encoded by RS frame units by the RS-CRC encoder 422 of thesecondary encoder 420, are outputted to the RS frame divider 423.

The RS frame divider 413 of the primary encoder 410 divides the primaryRS frame into several portions, which are then outputted to the outputmultiplexer (MUX) 320. Each portion of the primary RS frame isequivalent to a data amount that can be transmitted by one data group.Similarly, the RS frame divider 423 of the secondary encoder 420 dividesthe secondary RS frame into several portions, which are then outputtedto the output multiplexer (MUX) 320.

Hereinafter, the RS frame divider 413 of the primary RS encoder 410 willnow be described in detail. Also, in order to simplify the descriptionof the present invention, it is assumed that an RS frame payload havingthe size of N(row)×187(column), as shown in FIG. 19(a) to FIG. 19(c),that P number of parity data bytes are added to each column byRS-encoding the RS frame payload, and that a 2-byte checksum is added toeach row by CRC-encoding the RS frame payload. As a result, an RS framehaving the size of (N+2) (row)×187+P (column) is formed.

Accordingly, the RS frame divider 413 divides (or partitions) the RSframe having the size of (N+2) (row)×187+P (column) into severalportions, each having the size of PL (wherein PL corresponds to thelength of the RS frame portion).

At this point, as shown in Table 2 to Table 5, the value of PL may varydepending upon the RS frame mode, SCCC block mode, and SCCC outer codermode. Also, the total number of data bytes of the RS-encoded andCRC-encoded RS frame is equal to or smaller than 5×NoG×PL. In this case,the RS frame is divided (or partitioned) into ((5×NoG)−1) number ofportions each having the size of PL and one portion having a size equalto smaller than PL. More specifically, with the exception of the lastportion of the RS frame, each of the remaining portions of the RS framehas an equal size of PL.

If the size of the last portion is smaller than PL, a stuffing byte (ordummy byte) may be inserted in order to fill (or replace) the lackingnumber of data bytes, thereby enabling the last portion of the RS frameto also be equal to PL.

Each portion of an RS frame corresponds to the amount of data that areto be SCCC-encoded and mapped into a single data group of a parade.

FIG. 21(a) and FIG. 21(b) respectively illustrate examples of adding Snumber of stuffing bytes, when an RS frame having the size of(N+2)(row)×(187+P) (column) is divided into 5×NoG number of portions,each having the size of PL.

More specifically, the RS-encoded and CRC-encoded RS frame, shown inFIG. 21(a), is divided into several portions, as shown in FIG. 21(b).The number of divided portions at the RS frame is equal to (5×NoG).Particularly, the first ((5×NoG)−1) number of portions each has the sizeof PL, and the last portion of the RS frame may be equal to or smallerthan PL. If the size of the last portion is smaller than PL, a stuffingbyte (or dummy byte) may be inserted in order to fill (or replace) thelacking number of data bytes, as shown in Equation 4 below, therebyenabling the last portion of the RS frame to also be equal to PL.S=(5×NoG×PL)−((N+2)×(187+P))  Equation 4

Herein, each portion including data having the size of PL passes throughthe output multiplexer 320 of the M/H frame encoder 301, which is thenoutputted to the block processor 302.

At this point, the mapping order of the RS frame portions to a parade ofdata groups in not identical with the group assignment order defined inEquation 1. When given the group positions of a parade in an M/H frame,the SCCC-encoded RS frame portions will be mapped in a time order (i.e.,in a left-to-right direction).

Block Processor

Meanwhile, the block processor 302 performs an SCCC outer encodingprocess on the output of the M/H frame encoder 301. More specifically,the block processor 302 receives the data of each error correctionencoded portion. Then, the block processor 302 encodes the data onceagain at a coding rate of 1/H (wherein H is an integer equal to orgreater than 2 (i.e., H≧2)), thereby outputting the 1/H-rate encodeddata to the group formatter 303. According to the embodiment of thepresent invention, the input data are encoded either at a coding rate of1/2 (also referred to as “1/2-rate encoding”) or at a coding rate of 1/4(also referred to as “1/4-rate encoding”). The data of each portionoutputted from the M/H frame encoder 301 may include at least one ofmobile service data, RS parity data, CRC data, and stuffing data.However, in a broader meaning, the data included in each portion maycorrespond to data for mobile services. Therefore, the data included ineach portion will all be considered as mobile service data and describedaccordingly.

The group formatter 303 inserts the mobile service dataSCCC-outer-encoded and outputted from the block processor 302 in thecorresponding region within the data group, which is formed inaccordance with a pre-defined rule. Also, in association with the datadeinterleaving process, the group formatter 303 inserts various placeholders (or known data place holders) in the corresponding region withinthe data group. Thereafter, the group formatter 303 deinterleaves thedata within the data group and the place holders.

According to the present invention, with reference to data after beingdata-interleaved, as shown in FIG. 5, a data groups is configured of 10M/H blocks (B1 to B10) and divided into 4 regions (A, B, C, and D).

Also, as shown in FIG. 5, when it is assumed that the data group isdivided into a plurality of hierarchical regions, as described above,the block processor 302 may encode the mobile service data, which are tobe inserted to each region based upon the characteristic of eachhierarchical region, at different coding rates.

For example, the block processor 302 may encode the mobile service data,which are to be inserted in region A/B within the corresponding datagroup, at a coding rate of 1/2. Then, the group formatter 303 may insertthe 1/2-rate encoded mobile service data to region A/B. Also, the blockprocessor 302 may encode the mobile service data, which are to beinserted in region C/D within the corresponding data group, at a codingrate of 1/4 having higher (or stronger) error correction ability thanthe 1/2-coding rate. Thereafter, the group formatter 303 may insert the1/2-rate encoded mobile service data to region C/D. In another example,the block processor 302 may encode the mobile service data, which are tobe inserted in region C/D, at a coding rate having higher errorcorrection ability than the 1/4-coding rate. Then, the group formatter303 may either insert the encoded mobile service data to region C/D, asdescribed above, or leave the data in a reserved region for futureusage.

According to another embodiment of the present invention, the blockprocessor 302 may perform a 1/H-rate encoding process in SCCC blockunits. Herein, the SCCC block includes at least one M/H block.

At this point, when 1/H-rate encoding is performed in M/H block units,the M/H blocks (B1 to B10) and the SCCC block (SCB1 to SCB10) becomeidentical to one another (i.e., SCB1=B1, SCB2=B2, SCB3=B3, SCB4=B4,SCB5=B5, SCB6=B6, SCB7=B7, SCB8=B8, SCB9=B9, and SCB10=B10). Forexample, the M/H block 1 (B1) may be encoded at the coding rate of 1/2,the M/H block 2 (B2) may be encoded at the coding rate of 1/4, and theM/H block 3 (B3) may be encoded at the coding rate of 1/2. The codingrates are applied respectively to the remaining M/H blocks.

Alternatively, a plurality of M/H blocks within regions A, B, C, and Dmay be grouped into one SCCC block, thereby being encoded at a codingrate of 1/H in SCCC block units. Accordingly, the receiving performanceof region C/D may be enhanced. For example, M/H block 1 (B1) to M/Hblock 5 (B5) may be grouped into one SCCC block and then encoded at acoding rate of 1/2. Thereafter, the group formatter 303 may insert the1/2-rate encoded mobile service data to a section starting from M/Hblock 1 (B1) to M/H block 5 (B5).

Furthermore, M/H block 6 (B6) to M/H block 10 (B10) may be grouped intoone SCCC block and then encoded at a coding rate of 1/4. Thereafter, thegroup formatter 303 may insert the 1/4-rate encoded mobile service datato another section starting from M/H block 6 (B6) to M/H block 10 (B10).In this case, one data group may consist of two SCCC blocks.

According to another embodiment of the present invention, one SCCC blockmay be formed by grouping two M/H blocks. For example, M/H block 1 (B1)and M/H block 6 (B6) may be grouped into one SCCC block (SCB1).Similarly, M/H block 2 (B2) and M/H block 7 (B7) may be grouped intoanother SCCC block (SCB2). Also, M/H block 3 (B3) and M/H block 8 (B8)may be grouped into another SCCC block (SCB3). And, M/H block 4 (B4) andM/H block 9 (B9) may be grouped into another SCCC block (SCB4).Furthermore, M/H block 5 (B5) and M/H block 10 (B10) may be grouped intoanother SCCC block (SCB5). In the above-described example, the datagroup may consist of 10 M/H blocks and 5 SCCC blocks. Accordingly, in adata (or signal) receiving environment undergoing frequent and severechannel changes, the receiving performance of regions C and D, which isrelatively more deteriorated than the receiving performance of region A,may be reinforced. Furthermore, since the number of mobile service datasymbols increases more and more from region A to region D, the errorcorrection encoding performance becomes more and more deteriorated.Therefore, when grouping a plurality of M/H block to form one SCCCblock, such deterioration in the error correction encoding performancemay be reduced.

As described-above, when the block processor 302 performs encoding at a1/H-coding rate, information associated with SCCC should be transmittedto the receiving system in order to accurately recover the mobileservice data.

Table 7 below shows an example of a SCCC block mode, which indicatingthe relation between an M/H block and an SCCC block, among diverse SCCCblock information.

TABLE 7 SCCC Block Mode 00 01 10 11 Description One M/H Block Two M/HBlocks per SCCC Block per SCCC Block Reserved Reserved SCB SCB input,SCB input, M/H Block M/H Blocks SCB1 B1 B1 + B6 SCB2 B2 B2 + B7 SCB3 B3B3 + B8 SCB4 B4 B4 + B9 SCB5 B5 B5 + B10 SCB6 B6 — SCB7 B7 — SCB8 B8 —SCB9 B9 — SCB10 B10 —

More specifically, Table 4 shows an example of 2 bits being allocated inorder to indicate the SCCC block mode. For example, when the SCCC blockmode value is equal to ‘00’, this indicates that the SCCC block and theM/H block are identical to one another. Also, when the SCCC block modevalue is equal to ‘01’, this indicates that each SCCC block isconfigured of 2 M/H blocks.

As described above, if one data group is configured of 2 SCCC blocks,although it is not indicated in Table 7, this information may also beindicated as the SCCC block mode. For example, when the SCCC block modevalue is equal to ‘10’, this indicates that each SCCC block isconfigured of 5 M/H blocks and that one data group is configured of 2SCCC blocks. Herein, the number of M/H blocks included in an SCCC blockand the position of each M/H block may vary depending upon the settingsmade by the system designer. Therefore, the present invention will notbe limited to the examples given herein. Accordingly, the SCCC modeinformation may also be expanded.

An example of a coding rate information of the SCCC block, i.e., SCCCouter code mode, is shown in Table 8 below.

TABLE 8 SCCC outer code mode (2 bits) Description 00 Outer code rate ofSCCC block is 1/2 rate 01 Outer code rate of SCCC block is 1/4 rate 10Reserved 11 Reserved

More specifically, Table 8 shows an example of 2 bits being allocated inorder to indicate the coding rate information of the SCCC block. Forexample, when the SCCC outer code mode value is equal to ‘00’, thisindicates that the coding rate of the corresponding SCCC block is 1/2.And, when the SCCC outer code mode value is equal to ‘01’, thisindicates that the coding rate of the corresponding SCCC block is 1/4.

If the SCCC block mode value of Table 7 indicates ‘00’, the SCCC outercode mode may indicate the coding rate of each M/H block with respect toeach M/H block. In this case, since it is assumed that one data groupincludes 10 M/H blocks and that 2 bits are allocated for each SCCC blockmode, a total of 20 bits are required for indicating the SCCC blockmodes of the 10 M/H modes.

In another example, when the SCCC block mode value of Table 7 indicates‘00’, the SCCC outer code mode may indicate the coding rate of eachregion with respect to each region within the data group. In this case,since it is assumed that one data group includes 4 regions (i.e.,regions A, B, C, and D) and that 2 bits are allocated for each SCCCblock mode, a total of 8 bits are required for indicating the SCCC blockmodes of the 4 regions.

In another example, when the SCCC block mode value of Table 7 is equalto ‘01’, each of the regions A, B, C, and D within the data group hasthe same SCCC outer code mode.

Meanwhile, an example of an SCCC output block length (SOBL) for eachSCCC block, when the SCCC block mode value is equal to ‘00’, is shown inTable 9 below.

TABLE 9 SIBL SCCC Block SOBL 1/2 rate 1/4 rate SCB1 (B1) 528 264 132SCB2 (B2) 1536 768 384 SCB3 (B3) 2376 1188 594 SCB4 (B4) 2388 1194 597SCB5 (B5) 2772 1386 693 SCB6 (B6) 2472 1236 618 SCB7 (B7) 2772 1386 693SCB8 (B8) 2508 1254 627 SCB9 (B9) 1416 708 354 SCB10 (B10) 480 240 120

More specifically, when given the SCCC output block length (SOBL) foreach SCCC block, an SCCC input block length (SIBL) for eachcorresponding SCCC block may be decided based upon the outer coding rateof each SCCC block. The SOBL is equivalent to the number of SCCC output(or outer-encoded) bytes for each SCCC block. And, the SIBL isequivalent to the number of SCCC input (or payload) bytes for each SCCCblock.

Table 10 below shows an example of the SOBL and SIBL for each SCCCblock, when the SCCC block mode value is equal to ‘01’.

TABLE 10 SIBL SCCC Block SOBL 1/2 rate 1/4 rate SCB1 (B1 + B6) 528 264132 SCB2 (B2 + B7) 1536 768 384 SCB3 (B3 + B8) 2376 1188 594 SCB4 (B4 +B9) 2388 1194 597 SCB5 (B5 + B10) 2772 1386 693

In order to do so, as shown in FIG. 22, the block processor 302 includesa RS frame portion-SCCC block converter 511, a byte-bit converter 512, aconvolution encoder 513, a symbol interleaver 514, a symbol-byteconverter 515, and an SCCC block-M/H block converter 516.

The convolutional encoder 513 and the symbol interleaver 514 arevirtually concatenated with the trellis encoding module in thepost-processor in order to configure an SCCC block.

More specifically, the RS frame portion-SCCC block converter 511 dividesthe RS frame portions, which are being inputted, into multiple SCCCblocks using the SIBL of Table 9 and Table 10 based upon the RS codemode, SCCC block mode, and SCCC outer code mode. Herein, the M/H frameencoder 301 may output only primary RS frame portions or both primary RSframe portions and secondary RS frame portions in accordance with the RSframe mode.

When the RS Frame mode is set to ‘00’, a portion of the primary RS Frameequal to the amount of data, which are to be SCCC outer encoded andmapped to 10 M/H blocks (B1 to B10) of a data group, will be provided tothe block processor 302. When the SCCC block mode value is equal to‘00’, then the primary RS frame portion will be split into 10 SCCCBlocks according to Table 9. Alternatively, when the SCCC block modevalue is equal to ‘01’, then the primary RS frame will be split into 5SCCC blocks according to Table 10. When the RS frame mode value is equalto ‘01’, then the block processor 302 may receive two RS frame portions.The RS frame mode value of ‘01’ will not be used with the SCCC blockmode value of ‘01’. The first portion from the primary RS frame will beSCCC-outer-encoded as SCCC Blocks SCB3, SCB4, SCB5, SCB6, SCB7, and SCB8by the block processor 302. The SCCC Blocks SCB3 and SCB8 will be mappedto region B and the SCCC blocks SCB4, SCB5, SCB6, and SCB7 shall bemapped to region A by the group formatter 303. The second portion fromthe secondary RS frame will also be SCCC-outer-encoded, as SCB1, SCB2,SCB9, and SCB10, by the block processor 302. The group formatter 303will map the SCCC blocks SCB1 and SCB10 to region D as the M/H blocks B1and B10, respectively. Similarly, the SCCC blocks SCB2 and SCB9 will bemapped to region C as the M/H blocks B2 and B9.

The byte-bit converter 512 identifies the mobile service data bytes ofeach SCCC block outputted from the RS frame portion-SCCC block converter511 as data bits, which are then outputted to the convolution encoder513.

The convolution encoder 513 performs one of 1/2-rate encoding and1/4-rate encoding on the inputted mobile service data bits.

FIG. 23 illustrates a detailed block diagram of the convolution encoder513. The convolution encoder 513 includes two delay units 521 and 523and three exclusive-or gates 522, 524, and 525. Herein, the convolutionencoder 513 encodes an input data bit U and outputs the coded bit U to 5bits (u0 to u4).

At this point, the input data bit U is directly outputted as uppermostbit u0 and simultaneously encoded as lower bit u1u2u3u4 and thenoutputted. More specifically, the input data bit U is directly outputtedas the uppermost bit u0 and simultaneously outputted to the first andthird exclusive-or gates 522 and 525. The first exclusive-or gate 522performs exclusive-or operation on the input data bit U and the outputbit of the first delay unit 521 and, then, outputs to the second delayunit 523. Then, the data bit delayed by a pre-determined time (e.g., by1 clock) in the second delay unit 523 is outputted as a lower bit u1 andsimultaneously fed-back to the first delay unit 521. The first delayunit 521 delays the data bit fed-back from the second delay unit 523 bya pre-determined time (e.g., by 1 clock). Then, the first delay unit 521outputs the delayed data bit as a lower bit u2 and, at the same time,outputs the fed-back data to the first exclusive-or gate 522 and thesecond exclusive-or gate 524.

The second exclusive-or gate 524 performs exclusive-or operation on thedata bits outputted from the first and second delay units 521 and 523and outputs as a lower bit u3. The third exclusive-or gate 525 performson exclusive-or operation on the input data bit U and the output of thesecond delay unit 523 and outputs as a lower bit u4.

At this point, the first and second delay units 521 and 523 are reset to‘0’, at the starting point of each SCCC block. The convolution encoder513 of FIG. 23 may be used as a 1/2-rate encoder or a 1/4-rate encoder.

More specifically, when a portion of the output bit of the convolutionencoder 513, shown in FIG. 23, is selected and outputted, theconvolution encoder 513 may be used as one of a 1/2-rate encoder and a1/4-rate encoder.

Table 11 below shown an example of output symbols of the convolutionencoder 513.

TABLE 11 Reg 1/2 1/4 rate ion rate SCCC block mode = ‘00’ SCCC blockmode = ‘01’ A, B (u0, u1) (u0, u2), (u1, u3) (u0, u2), (u1, u4) C, D(u0, u1), (u3, u4)

For example, at the 1/2-coding rate, 1 output symbol (i.e., u0 and u1bits) may be selected and outputted. And, at the 1/4-coding rate,depending upon the SCCC block mode, 2 output symbols (i.e., 4 bits) maybe selected and outputted. For example, when the SCCC block mode valueis equal to ‘01’, and when an output symbol configured of u0 and u2 andanother output symbol configured of u1 and u4 are selected andoutputted, a 1/4-rate coding result may be obtained.

The mobile service data encoded at the coding rate of 1/2 or 1/4 by theconvolution encoder 513 are outputted to the symbol interleaver 514.

The symbol interleaver 514 performs block interleaving, in symbol units,on the output data symbol of the convolution encoder 513. Morespecifically, the symbol interleaver 514 is a type of block interleaver.Any interleaver performing structural rearrangement (or realignment) maybe applied as the symbol interleaver 514 of the block processor.However, in the present invention, a variable length symbol interleaverthat can be applied even when a plurality of lengths is provided for thesymbol, so that its order may be rearranged, may also be used.

FIG. 24 illustrates a symbol interleaver according to an embodiment ofthe present invention. Particularly, FIG. 30 illustrates an example ofthe symbol interleaver when B=2112 and L=4096.

Herein, B indicates a block length in symbols that are outputted forsymbol interleaving from the convolution encoder 513. And, L representsa block length in symbols that are actually interleaved by the symbolinterleaver 514. At this point, the block length in symbols B inputtedto the symbol interleaver 514 is equivalent to 4×SOBL. Morespecifically, since one symbol is configured of 2 bits, the value of Bmay be set to be equal to 4×SOBL.

In the present invention, when performing the symbol-interleavingprocess, the conditions of L=2^(m) (wherein m is an integer) and of L≧Bshould be satisfied. If there is a difference in value between B and L,(L−B) number of null (or dummy) symbols is added, thereby creating aninterleaving pattern, as shown in P′(i) of FIG. 24.

Therefore, B becomes a block size of the actual symbols that areinputted to the symbol interleaver 514 in order to be interleaved. Lbecomes an interleaving unit when the interleaving process is performedby an interleaving pattern created from the symbol interleaver 514.

Equation 5 shown below describes the process of sequentially receiving Bnumber of symbols, the order of which is to be rearranged, and obtainingan L value satisfying the conditions of L=2^(m) (wherein m is aninteger) and of thereby creating the interleaving so as to realign (orrearrange) the symbol order.

In relation to all places, wherein 0≦i≦B−1,P′(i)={89×i×(i+1)/2} mod L  Equation 5

Herein, L≧B, L=2^(m), wherein m is an integer.

As shown in P′(i) of FIG. 24 and Equation 5, the order of B number ofinput symbols and (L−B) number of null symbols is rearranged by usingthe above-mentioned Equation 6. Then, as shown in P(i) of FIG. 24, thenull byte places are removed, so as to rearrange the order. Startingwith the lowest value of i, the P(i) are shifted to the left in order tofill the empty entry locations. Thereafter, the symbols of the alignedinterleaving pattern P(i) are outputted to the symbol-byte converter 515in order.

Herein, the symbol-byte converter 515 converts to bytes the mobileservice data symbols, having the rearranging of the symbol ordercompleted and then outputted in accordance with the rearranged order,and thereafter outputs the converted bytes to the SCCC block-M/H blockconverter 516. The SCCC block-M/H block converter 516 converts thesymbol-interleaved SCCC blocks to M/H blocks, which are then outputtedto the group formatter 303.

If the SCCC block mode value is equal to ‘00’, the SCCC block is mappedat a one-to-one (1:1) correspondence with each M/H block within the datagroup. In another example, if the SCCC block mode value is equal to‘01’, each SCCC block is mapped with two M/H blocks within the datagroup. For example, the SCCC block SCB1 is mapped with (B1, B6), theSCCC block SCB2 is mapped with (B2, B7), the SCCC block SCB3 is mappedwith (B3, B8), the SCCC block SCB4 is mapped with (B4, B9), and the SCCCblock SCB5 is mapped with (B5, B10). The M/H block that is outputtedfrom the SCCC block-M/H block converter 516 is configured of mobileservice data and FEC redundancy. In the present invention, the mobileservice data as well as the FEC redundancy of the M/H block will becollectively considered as mobile service data.

Group Formatter

The group formatter 303 inserts data of M/H blocks outputted from theblock processor 302 to the corresponding M/H blocks within the datagroup, which is formed in accordance with a pre-defined rule. Also, inassociation with the data-deinterleaving process, the group formatter303 inserts various place holders (or known data place holders) in thecorresponding region within the data group.

More specifically, apart from the encoded mobile service data outputtedfrom the block processor 302, the group formatter 303 also inserts MPEGheader place holders, non-systematic RS parity place holders, mainservice data place holders, which are associated with the datadeinterleaving in a later process, as shown in FIG. 5. Herein, the mainservice data place holders are inserted because the mobile service databytes and the main service data bytes are alternately mixed with oneanother in regions B to D based upon the input of the datadeinterleaver, as shown in FIG. 5. For example, based upon the dataoutputted after data deinterleaving, the place holder for the MPEGheader may be allocated at the very beginning of each packet. Also, inorder to configure an intended group format, dummy bytes may also beinserted. Furthermore, the group formatter 303 inserts initializationdata (i.e., trellis initialization byte) of the trellis encoding module256 in the corresponding regions. For example, the initialization datamay be inserted in the beginning of the known data sequence. Theinitialization data is used for initializing memories within the trellisencoding module 256, and is not transmitted to the receiving system.

Additionally, the group formatter 303 may also insert signalinginformation, which are encoded and outputted from the signaling encoder304, in corresponding regions within the data group.

At this point, reference may be made to the signaling information whenthe group formatter 303 inserts each data type and respective placeholders in the data group. The process of encoding the signalinginformation and inserting the encoded signaling information to the datagroup will be described in detail in a later process.

After inserting each data type and respective place holders in the datagroup, the group formatter 303 may deinterleave the data and respectiveplace holders, which have been inserted in the data group, as an inverseprocess of the data interleaver, thereby outputting the deinterleaveddata and respective place holders to the packet formatter 305. The groupformatter 303 may include a group format organizer 527, and a datadeinterleaver 529, as shown in FIG. 25. The group format organizer 527inserts data and respective place holders in the corresponding regionswithin the data group, as described above. And, the data deinterleaver529 deinterleaves the inserted data and respective place holders as aninverse process of the data interleaver.

The packet formatter 305 removes the main service data place holders andthe RS parity place holders and replaces the MPEG header place holderswith MPEG header that were allocated for the deinterleaving process fromthe deinterleaved data being inputted.

Also, when the group formatter 303 inserts known data place holders, thepacket formatter 303 may insert actual known data in the known dataplace holders, or may directly output the known data place holderswithout any modification in order to make replacement insertion in alater process.

Thereafter, the packet formatter 305 identifies the data within thepacket-formatted data group, as described above, as a 188-byte unitmobile service data packet (i.e., MPEG TS packet), which is thenprovided to the packet multiplexer 240.

The packet multiplexer 240 multiplexes the mobile service data packetspacket-formatted and outputted from the packet formatter 306 and mainservice data packets outputted from the packet jitter mitigator 220.Then, the packet multiplexer 240 outputs the multiplexed data packets tothe data randomizer 251 of the post-processor 250. If the packetmultiplexer 240 receives 118 mobile service data packets from the packetformatter 305, 37 mobile service data packets are placed before a placefor inserting VSB field synchronization. Then, the remaining 81 mobileservice data packets are placed after the place for inserting VSB fieldsynchronization. The multiplexing method may be adjusted by diversevariables of the system design. The multiplexing method and multiplexingrule of the packet multiplexer 240 will be described in more detail in alater process.

Also, since a data group including mobile service data in-between thedata bytes of the main service data is multiplexed (or allocated) duringthe packet multiplexing process, the shifting of the chronologicalposition (or place) of the main service data packet becomes relative.Also, a system object decoder (i.e., MPEG decoder) for processing themain service data of the receiving system, receives and decodes only themain service data and recognizes the mobile service data packet as anull data packet.

Therefore, when the system object decoder of the receiving systemreceives a main service data packet that is multiplexed with the datagroup, a packet jitter occurs.

At this point, since a multiple-level buffer for the video data existsin the system object decoder and the size of the buffer is relativelylarge, the packet jitter generated from the packet multiplexer 240 doesnot cause any serious problem in case of the video data. However, sincethe size of the buffer for the audio data in the object decoder isrelatively small, the packet jitter may cause considerable problem.

More specifically, due to the packet jitter, an overflow or underflowmay occur in the buffer for the main service data of the receivingsystem (e.g., the buffer for the audio data).

Therefore, the packet jitter mitigator 220 re-adjusts the relativeposition of the main service data packet so that the overflow orunderflow does not occur in the system object decoder.

In the present invention, examples of repositioning places for the audiodata packets within the main service data in order to minimize theinfluence on the operations of the audio buffer will be described indetail. The packet jitter mitigator 220 repositions the audio datapackets in the main service data section so that the audio data packetsof the main service data can be as equally and uniformly aligned andpositioned as possible.

Additionally, when the positions of the main service data packets arerelatively re-adjusted, associated program clock reference (PCR) valuesmay also be modified accordingly. The PCR value corresponds to a timereference value for synchronizing the time of the MPEG decoder. Herein,the PCR value is inserted in a specific region of a TS packet and thentransmitted. In the example of the present invention, the packet jittermitigator 220 also performs the operation of modifying the PCR value.

The output of the packet jitter mitigator 220 is inputted to the packetmultiplexer 240. As described above, the packet multiplexer 240multiplexes the main service data packets outputted from the packetjitter mitigator 220 with the mobile service data packets outputted fromthe pre-processor 230 into a burst structure in accordance with apre-determined multiplexing rule. Then, the packet multiplexer 240outputs the multiplexed data packets to the data randomizer 251 of thepost-processor 250.

If the inputted data correspond to the main service data packet, thedata randomizer 251 performs the same randomizing process as that of theconventional randomizer and outputs to the RS encoder/non-systematic RSencoder 252. More specifically, all data bytes of the main service datapacket are randomized by using a pseudo random byte generated from thedata randomizer 251. Thereafter, the randomized data are outputted tothe RS encoder/non-systematic RS encoder 252. On the other hand, if theinputted data correspond to the mobile service data packet, the datarandomizer 251 performs randomizing only MPEG header byte of the mobileservice data packet and outputs to the RS encoder/non-systematic RSencoder 252. The randomizing of the mobile service data included in themobile service data packet was performed by the data randomizer 411 ofthe primary encoder 410 and/or the data randomizer 422 of the secondaryencoder 420.

The RS encoder/non-systematic RS encoder 252 performs an RS encodingprocess on the data being randomized by the data randomizer 251 or onthe data bypassing the data randomizer 251, so as to add 20 bytes of RSparity data. Thereafter, the processed data are outputted to the datainterleaver 253. Herein, if the inputted data correspond to the mainservice data packet, the RS encoder/non-systematic RS encoder 252performs the same systematic RS encoding process as that of theconventional broadcasting system, thereby adding the 20-byte RS paritydata at the end of the 187-byte data. Alternatively, if the inputteddata correspond to the mobile service data packet, the RSencoder/non-systematic RS encoder 252 performs a non-systematic RSencoding process. At this point, the 20-byte RS parity data obtainedfrom the non-systematic RS encoding process are inserted in apre-decided parity byte place within the mobile service data packet.

The data interleaver 253 corresponds to a byte unit convolutionalinterleaver.

The output of the data interleaver 253 is inputted to the parityreplacer 254 and to the non-systematic RS encoder 255.

Meanwhile, a process of initializing a memory within the trellisencoding module 256 is primarily required in order to decide the outputdata of the trellis encoding module 256, which is located after theparity replacer 254, as the known data pre-defined according to anagreement between the receiving system and the transmitting system. Morespecifically, the memory of the trellis encoding module 256 should firstbe initialized before the received known data sequence istrellis-encoded.

At this point, the beginning portion of the known data sequence that isreceived corresponds to the initialization data (i.e., trellisinitialization data bytes) and not to the actual known data. Herein, theinitialization data has been included in the data by the group formatterwithin the pre-processor 230 in an earlier process. Therefore, theprocess of replacing the initialization data with memory values withinthe trellis encoding module 256 are required to be performed immediatelybefore the inputted known data sequence is trellis-encoded.

More specifically, the initialization data are replaced with the memoryvalue within the trellis encoding module 256, thereby being inputted tothe trellis encoding module 256. At this point, the memory valuereplacing the initialization data are process with (or calculated by) anexclusive OR (XOR) operation with the respective memory value within thetrellis encoding module 256, so as to be inputted to the correspondingmemory. Therefore, the corresponding memory is initialized to ‘0’.Additionally, a process of using the memory value replacing theinitialization data to re-calculate the RS parity, so that there-calculated RS parity value can replace the RS parity being outputtedfrom the data interleaver 253, is also required.

Therefore, the non-systematic RS encoder 255 receives the mobile servicedata packet including the initialization data from the data interleaver253 and also receives the memory value from the trellis encoding module256. Among the inputted mobile service data packet, the initializationdata are replaced with the memory value, and the RS parity data that areadded to the mobile service data packet are removed and processed withnon-systematic RS encoding. Thereafter, the new RS parity obtained byperforming the non-systematic RS encoding process is outputted to theparity replacer 255. Accordingly, the parity replacer 255 selects theoutput of the data interleaver 253 as the data within the mobile servicedata packet, and the parity replacer 255 selects the output of thenon-systematic RS encoder 255 as the RS parity. The selected data arethen outputted to the trellis encoding module 256.

Meanwhile, if the main service data packet is inputted or if the mobileservice data packet, which does not include any initialization data thatare to be replaced, is inputted, the parity replacer 254 selects thedata and RS parity that are outputted from the data interleaver 253.Then, the parity replacer 254 directly outputs the selected data to thetrellis encoding module 256 without any modification.

The trellis encoding module 256 converts the byte-unit data to symbolunits and performs a 12-way interleaving process so as to trellis-encodethe received data. Thereafter, the processed data are outputted to thesynchronization multiplexer 260.

FIG. 26 illustrates a detailed diagram of one of 12 trellis encodersincluded in the trellis encoding module 256. Herein, the trellis encoderincludes first and second multiplexers 531 and 541, first and secondexclusive OR (XOR) gates 532 and 542, and first to third memories 533,542, and 544.

More specifically, the first to third memories 533, 542, and 544 areinitialized by the memory value instead of the initialization data fromthe parity replacer 254. More specifically, when the first symbol (i.e.,two bits), which are converted from initialization data (i.e., eachtrellis initialization data byte), are inputted, the input bits of thetrellis encoder will be replaced by the memory values of the trellisencoder, as shown in FIG. 26.

Since 2 symbols (i.e., 4 bits) are required for trellis initialization,the last 2 symbols (i.e., 4 bits) from the trellis initialization bytesare not used for trellis initialization and are considered as a symbolfrom a known data byte and processed accordingly.

When the trellis encoder of FIG. 26 is in the initialization mode, theinput comes from an internal trellis status (or state) and not from theparity replacer 254. When the trellis encoder is in the normal mode, theinput symbol (X2X1) provided from the parity replacer 254 will beprocessed. The trellis encoder provides the converted (or modified)input data for trellis initialization to the non-systematic RS encoder255.

More specifically, when a selection signal designates a normal mode, thefirst multiplexer 531 selects an upper bit X2 of the input symbol. And,when a selection signal designates an initialization mode, the firstmultiplexer 531 selects the output of the first memory 533 and outputsthe selected output data to the first XOR gate 532. The first XOR gate532 performs XOR operation on the output of the first multiplexer 531and the output of the first memory 533, thereby outputting the addedresult to the first memory 533 and, at the same time, as a mostsignificant (or uppermost) bit Z2. The first memory 533 delays theoutput data of the first XOR gate 532 by 1 clock, thereby outputting thedelayed data to the first multiplexer 531 and the first XOR gate 532.Meanwhile, when a selection signal designates a normal mode, the secondmultiplexer 541 selects a lower bit X1 of the input symbol. And, when aselection signal designates an initialization mode, the secondmultiplexer 541 selects the output of the second memory 542, therebyoutputting the selected result to the second XOR gate 543 and, at thesame time, as a lower bit Z1. The second XOR gate 543 performs XORoperation on the output of the second multiplexer 541 and the output ofthe second memory 542, thereby outputting the added result to the thirdmemory 544. The third memory 544 delays the output data of the secondXOR gate 543 by 1 clock, thereby outputting the delayed data to thesecond memory 542 and, at the same time, as a least significant (orlowermost) bit Z0. The second memory 542 delays the output data of thethird memory 544 by 1 clock, thereby outputting the delayed data to thesecond XOR gate 543 and the second multiplexer 541.

The select signal designates an initialization mode during the first twosymbols that are converted from the initialization data.

For example, when the select signal designates an initialization mode,the first XOR gate 532 performs an XOR operation on the value of thefirst memory 533, which is provided through the first multiplexer 531,and on a memory value that is directly provided from the first memory533. That is, the first XOR gate 532 performs an XOR operation on 2 bitshaving the same value. Generally, when only one of the two bitsbelonging to the operand is ‘1’, the result of the XOR gate is equal to‘1’. Otherwise, the result of the XOR gate becomes equal to ‘0’.Therefore, when the value of the first memory 533 is processed with anXOR operation, the result is always equal to ‘0’. Furthermore, since theoutput of the first XOR gate 532, i.e., ‘0’, is inputted to the firstmemory 533, the first memory 533 is initialized to ‘0’.

Similarly, when the select signal designates an initialization mode, thesecond XOR gate 543 performs an XOR operation on the value of the secondmemory 542, which is provided through the second multiplexer 541, and ona memory value that is directly provided from the second memory 542.Therefore, the output of the second XOR gate 543 is also always equal to‘0’. Since the output of the second XOR gate 543, i.e., ‘0’, is inputtedto the third memory 544, the third memory 544 is also initialized to‘0’. The output of the third memory 544 is inputted to the second memory542 in the next clock, thereby initializing the second memory 542 to‘0’. In this case also, the select signal designates the initializationmode.

More specifically, when the first symbol being converted from theinitialization data byte replaces the values of the first memory 533 andthe second memory 542, thereby being inputted to the trellis encoder,each of the first and third memories 533 and 544 within the trellisencoder is initialized to ‘00’. Following the process, when the secondsymbol being converted from the initialization data byte replaces thevalues of the first memory 533 and the second memory 542, thereby beinginputted to the trellis encoder, each of the first, second, and thirdmemories 533, 542, and 544 within the trellis encoder is initialized to‘000’. As described above, 2 symbols are required to initialize thememory of the trellis encoder. At this point, while the select signaldesignates an initialization mode, the output bits (X2′X1′) of the firstand second memories 533 and 542 are inputted to the non-systematic RSencoder 255, so as to perform a new RS parity calculation process.

The synchronization multiplexer 260 inserts a field synchronizationsignal and a segment synchronization signal to the data outputted fromthe trellis encoding module 256 and, then, outputs the processed data tothe pilot inserter 271 of the transmission unit 270.

Herein, the data having a pilot inserted therein by the pilot inserter271 are modulated by the modulator 272 in accordance with apre-determined modulating method (e.g., a VSB method). Thereafter, themodulated data are transmitted to each receiving system though the radiofrequency (RF) up-converter 273.

Assignment of Known Data (or Training Signal)

The transmission system inserts long and regularly spaced trainingsequences (i.e., known data sequences) into each data group. Each datagroup contains 6 training sequences. The training sequences arespecified before trellis-encoding. The training sequences are thentrellis-encoded and these trellis-encoded sequences also are knownsequences. This is because the trellis encoder memories are initializedto pre-determined values at the beginning of each sequence. The form ofthe 6 training sequences at the byte level (before trellis-encoding) isshown in FIG. 27. FIG. 27 is an embodiment of the arrangement of thetraining sequences that is performed by the group formatter 303.

The 1^(st) training sequence is located at the last 2 segments of the3^(rd) M/H block (B3). The 2^(nd) training sequence may be inserted atthe 2^(nd) and 3^(rd) segments of the 4^(th) M/H block (B4). The 2^(nd)training sequence is next to the signaling area, as shown in FIG. 5.Then, the 3^(rd) training sequence, the 4^(th) training sequence, the5^(th) training sequence, and the 6^(th) training sequence may be placedat the last 2 segments of the 4^(th), 5^(th), 6^(th), and 7^(th) M/Hblocks (B4, B5, B6, and B7), respectively.

As shown in FIG. 27, the 1^(st) training sequence, the 3^(rd) trainingsequence, the 4^(th) training sequence, the 5^(th) training sequence,and the 6^(th) training sequence are spaced 16 segments apart from oneanother. Referring to FIG. 27, the dotted area indicates trellisinitialization data bytes, the lined area indicates training data bytes,and the white area includes other bytes such as the FEC-coded M/Hservice data bytes, FEC-coded signaling data, main service data bytes,RS parity data bytes (for backwards compatibility with legacy ATSCreceivers) and/or dummy data bytes.

FIG. 28 illustrates the training sequences (at the symbol level) aftertrellis-encoding by the trellis encoder. Referring to FIG. 28, thedotted area indicates data segment sync symbols, the lined areaindicates training data symbols, and the white area includes othersymbols, such as FEC-coded mobile service data symbols, FEC-codedsignaling data symbols, main service data symbols, RS parity datasymbols, dummy data symbols, trellis initialization data symbols, and/orthe first part of the training sequence data symbols.

After the trellis-encoding process, the last 1416 (=588+828) symbols ofthe 1^(st) training sequence, the 3^(rd) training sequence, the 4^(th)training sequence, the 5^(th) training sequence, and the 6^(th) trainingsequence commonly share the same data pattern. The 2^(nd) trainingsequence has a first 528-symbol sequence and a second 528-symbolsequence that have the same data pattern.

More specifically, the 528-symbol sequence is repeated after the4-symbol data segment synchronization signal. At the end of eachtraining sequence, the memory contents of the twelve modified trellisencoders shall be set to zero (0).

Processing Signaling Information

The present invention assigns signaling information areas for insertingsignaling information to some areas within each data group.

FIG. 29 illustrates an example of assigning signaling information areasfor inserting signaling information starting from the 1^(st) segment ofthe 4^(th) M/H block (B4) to a portion of the 2^(nd) segment. Morespecifically, 276(=207+69) bytes of the 4^(th) M/H block (B4) in eachdata group are assigned as the signaling information area. In otherwords, the signaling information area consists of 207 bytes of the1^(st) segment and the first 69 bytes of the 2^(nd) segment of the4^(th) M/H block (B4). For example, the 1^(st) segment of the 4^(th) M/Hblock (B4) corresponds to the 17^(th) or 173^(rd) segment of a VSBfield.

For example, when the data group includes 6 known data sequences, asshown in FIG. 27 and FIG. 28, the signaling information area is locatedbetween the first known data sequence and the second known datasequence. More specifically, the first known data sequence is insertedin the last 2 segments of the 3^(rd) M/H block (B3), and the secondknown data sequence in inserted in the 2^(nd) and 3^(rd) segments of the4^(th) M/H block (B4). Furthermore, the 3^(rd) to 6^(th) known datasequences are respectively inserted in the last 2 segments of each ofthe 4^(th), 5^(th), 6^(th), and 7^(th) M/H blocks (B4, B5, B6, and B7).The 1^(st) and 3^(rd) to 6^(th) known data sequences are spaced apart by16 segments.

The signaling information that is to be inserted in the signalinginformation area is FEC-encoded by the signaling encoder 304, therebyinputted to the group formatter 303.

The group formatter 303 inserts the signaling information, which isFEC-encoded and outputted by the signaling encoder 304, in the signalinginformation area within the data group.

Herein, the signaling information may be identified by two differenttypes of signaling channels: a transmission parameter channel (TPC) anda fast information channel (FIC).

Herein, the TPC data is transmitted through the TPC and corresponds tosignaling information including transmission parameters, such as RSframe information, RS encoding information, FIC information, data groupinformation, SCCC information, and M/H frame information and so on.However, the TPC data presented herein is merely exemplary. And, sincethe adding or deleting of signaling information included in the TPC maybe easily adjusted and modified by one skilled in the art, the presentinvention will, therefore, not be limited to the examples set forthherein. Also, the TPC data includes parameters that are mostly used in aphysical layer module. And, since the TPC data are transmitted withoutbeing interleaved, the TPC data may be accessed by slot unit in thereceiving system.

Furthermore, the FIC data is transmitted through the FIC and is providedto enable a fast service acquisition of data receivers, and the FIC dataincludes cross layer information between the physical layer and theupper layer(s).

FIG. 30 illustrates a detailed block diagram of the signaling encoder304 according to the present invention.

Referring to FIG. 34, the signaling encoder 304 includes a TPC encoder561, an FIC encoder 562, a block interleaver 563, a multiplexer 564, asignaling randomizer 565, and an iterative turbo encoder 566.

The TPC encoder 561 receives 10-bytes of TPC data and performs(18,10)-RS encoding on the 10-bytes of TPC data, thereby adding 8 bytesof RS parity data to the 10 bytes of TPC data. The 18 bytes ofRS-encoded TPC data are outputted to the multiplexer 564.

The FIC encoder 562 receives 37-bytes of FIC data and performs(51,37)-RS encoding on the 37-bytes of FIC data, thereby adding 14 bytesof RS parity data to the 37 bytes of FIC data. Thereafter, the 51 bytesof RS-encoded FIC data are inputted to the block interleaver 563,thereby being interleaved in predetermined block units. Herein, theblock interleaver 563 corresponds to a variable length blockinterleaver. The block interleaver 563 interleaves the FIC data withineach sub-frame in TNoG(column)×51(row) block units and then outputs theinterleaved data to the multiplexer 564. Herein, the TNoG corresponds tothe total number of data groups being assigned to a sub-frame. The blockinterleaver 563 is synchronized with the first set of FIC data in eachsub-frame.

The block interleaver 563 writes 51 bytes of incoming (or inputted) RScodewords in a row direction (i.e., row-by-row) and left-to-right andup-to-down directions and reads 51 bytes of RS codewords in a columndirection (i.e., column-by-column) and left-to-right and up-to-downdirections, thereby outputting the RS codewords.

The multiplexer 564 multiplexes the RS-encoded TPC data from the TPCencoder 561 and the block-interleaved FIC data from the blockinterleaver 563 along a time axis. Then, the multiplexer 564 outputs 69bytes of the multiplexed data to the signaling randomizer 565.

The signaling randomizer 565 randomizes the multiplexed data and outputsthe randomized data to the iterative turbo encoder 566. The signalingrandomizer 565 may use the same generator polynomial of the randomizerused for mobile service data. Also, initialization occurs in each datagroup.

The iterative turbo encoder 566 corresponds to an inner encoderperforming iterative turbo encoding in a PCCC method on the randomizeddata (i.e., signaling information data). The iterative turbo encoder 566may include 6 even component encoders and 6 odd component encoders.

FIG. 31 illustrates an example of a syntax structure of TPC data beinginputted to the TPC encoder 561.

The TPC data are inserted in the signaling information area of each datagroup and then transmitted. The TPC data may include a sub-frame_numberfield, a slot_number field, a parade_id field, a starting_group_number(SGN) field, a number_of_groups (NoG) field, a parade_repetition_cycle(PRC) field, an RS_frame_mode field, an RS_code_mode_primary field, anRS_code_mode_secondary field, an SCCC_block_mode field, anSCCC_outer_code_mode_A field, an SCCC_outer_code_mode_B field, anSCCC_outer_code_mode_C field, an SCCC_outer_code_mode_D field, anFIC_version field, a parade_continuity_counter field, and a TNoG field.

The Sub-Frame_number field corresponds to the current Sub-Frame numberwithin the M/H frame, which is transmitted for M/H framesynchronization. The value of the Sub-Frame_number field may range from0 to 4.

The Slot_number field indicates the current slot number within thesub-frame, which is transmitted for M/H frame synchronization. Also, thevalue of the Sub-Frame_number field may range from 0 to 15.

The Parade_id field identifies the parade to which this group belongs.The value of this field may be any 7-bit value. Each parade in a M/Htransmission shall have a unique Parade_id field. Communication of theParade_id between the physical layer and the management layer may beperformed by means of an Ensemble_id field formed by adding one bit tothe left of the Parade_id field. If the Ensemble_id field is used forthe primary Ensemble delivered through this parade, the added MSB shallbe equal to ‘0’. Otherwise, if the Ensemble_id field is used for thesecondary ensemble, the added MSB shall be equal to ‘1’. Assignment ofthe Parade_id field values may occur at a convenient level of thesystem, usually in the management layer.

The starting_group_number (SGN) field shall be the first Slot_number fora parade to which this group belongs, as determined by Equation 1 (i.e.,after the Slot numbers for all preceding parades have been calculated).The SGN and NoG shall be used according to Equation 1 to obtain the slotnumbers to be allocated to a parade within the sub-frame.

The number_of_Groups (NoG) field shall be the number of groups in asub-frame assigned to the parade to which this group belongs, minus 1,e.g., NoG=0 implies that one group is allocated (or assigned) to thisparade in a sub-frame. The value of NoG may range from 0 to 7. Thislimits the amount of data that a parade may take from the main (legacy)service data, and consequently the maximum data that can be carried byone parade. The slot numbers assigned to the corresponding Parade can becalculated from SGN and NoG, using Equation 1. By taking each parade insequence, the specific slots for each parade will be determined, andconsequently the SGN for each succeeding parade. For example, if for aspecific parade SGN=3 and NoG=3 (010b for 3-bit field of NoG),substituting=3, 4, and 5 in Equation 1 provides slot numbers 12, 2, and6.

The Parade_repetition_cycle (PRC) field corresponds to the cycle timeover which the parade is transmitted, minus 1, specified in units of M/Hframes, as described in Table 12.

TABLE 12 PRC Description 000 This parade shall be transmitted once everyM/H frame. 001 This parade shall be transmitted once every 2 M/H frames.010 This parade shall be transmitted once every 3 M/H frames. 011 Thisparade shall be transmitted once every 4 M/H frames. 100 This paradeshall be transmitted once every 5 M/H frames. 101 This parade shall betransmitted once every 6 M/H frames. 110 This parade shall betransmitted once every 7 M/H frames. 111 Reserved

For example, if PRC field value is equal to ‘001’, this indicates thatthe parade shall be transmitted once every 2 M/H frame.

The RS_Frame_mode field shall be as defined in Table 1. TheRS_Frame_mode field represents that one parade transmits one RS frame ortwo RS frames.

The RS_code_mode_primary field shall be the RS code mode for the primaryRS frame. Herein, the RS_code_mode_primary field is defined in Table 6.

The RS_code_mode_secondary field shall be the RS code mode for thesecondary RS frame. Herein, the RS_code_mode_secondary field is definedin Table 6.

The SCCC_Block_mode field represents how M/H blocks within a data groupare assigned to SCCC block. The SCCC_Block_mode field shall be asdefined in Table 7.

The SCCC_outer_code_mode_A field corresponds to the SCCC outer code modefor Region A within a data group. The SCCC outer code mode is defined inTable 8.

The SCCC_outer_code_mode_B field corresponds to the SCCC outer code modefor Region B within the data group.

The SCCC_outer_code_mode_C field corresponds be the SCCC outer code modefor Region C within the data group.

And, the SCCC_outer_code_mode_D field corresponds to the SCCC outer codemode for Region D within the data group.

The FIC_version field represents a version of FIC data.

The Parade_continuity_counter field counter may increase from 0 to 15and then repeat its cycle. This counter shall increment by 1 every(PRC+1) M/H frames. For example, as shown in Table 12, PRC=011 (decimal3) implies that Parade_continuity_counter increases every fourth M/Hframe.

The TNoG field may be identical for all sub-frames in an M/H Frame.

However, the information included in the TPC data presented herein ismerely exemplary. And, since the adding or deleting of informationincluded in the TPC may be easily adjusted and modified by one skilledin the art, the present invention will, therefore, not be limited to theexamples set forth herein.

Since the TPC data (excluding the Sub-Frame_number field and theSlot_number field) for each parade do not change their values during anM/H frame, the same information is repeatedly transmitted through allM/H groups belonging to the corresponding parade during an M/H frame.This allows very robust and reliable reception of the TPC data. Becausethe Sub-Frame_number and the Slot_number are increasing counter values,they also are robust due to the transmission of regularly expectedvalues. Furthermore, the FIC data is provided to enable a fast serviceacquisition of data receivers, and the FIC information includes crosslayer information between the physical layer and the upper layer(s).

FIG. 32 illustrates an example of a transmission scenario of the TPCdata and the FIC data. The values of the Sub-Frame_number field,Slot_number field, Parade_id field, Parade_repetition_cycle field, andParade_continuity_counter field may corresponds to the current M/H framethroughout the sub-frames within a specific M/H frame. Some of TPCparameters and FIC data are signaled in advance.

The SGN, NoG and all FEC modes may have values corresponding to thecurrent M/H frame in the first two sub-frames. The SGN, NoG and all FECmodes may have values corresponding to the frame in which the paradenext appears throughout the 3^(rd), 4^(th) and 5^(th) sub-frames of thecurrent M/H frame. This enables the M/H receivers to receive (oracquire) the transmission parameters in advance very reliably.

For example, when Parade_repetition_cycle=‘000’, the values of the3^(rd), 4^(th), and 5^(th) sub-frames of the current M/H framecorrespond to the next M/H frame. Also, whenParade_repetition_cycle=‘011’, the values of the 3^(rd), 4^(th), and5^(th) sub-frames of the current M/H frame correspond to the 4^(th) M/Hframe and beyond.

The FIC_version field and the FIC_data field may have values that applyto the current M/H Frame during the 1^(st) sub-frame and the 2^(nd)sub-frame, and they shall have values corresponding to the M/H frameimmediately following the current M/H frame during the 3^(rd), 4^(th),and 5^(th) sub-frames of the current M/H frame.

Meanwhile, FIC data being transmitted through the FIC, i.e., an FICchunk uses its fast characteristic so as to deliver mapping (or binding)information between a mobile service and an ensemble to the receivingsystem. More specifically, the FIC chunk corresponds to signaling dataused for enabling the receiving system to swiftly find an ensemble thatdelivers a wanted (or desired) mobile service and to swiftly receive RSframes of the corresponding ensemble. At this point, the FIC chunk issegmented into a plurality of FIC segment payloads and a plurality ofFIC segments are formed by added each FIC segment header to each FICsegment payload. Furthermore, one FIC segment is transmitted through onedata group.

FIG. 33 illustrates a syntax structure of an FIC chunk that maps therelation between a mobile service and an ensemble through the FIC.

Herein, the FIC chunk consists of a 5-byte FIC chunk header and an FICchunk payload having variable-length.

FIG. 34 illustrates a syntax structure of an FIC chunk header accordingto an embodiment of the present invention.

Herein, the FIC chunk header signals a non-backward compatible majorprotocol version change in a corresponding FIC chunk and also signals abackward compatible minor protocol version change. Furthermore, the FICchunk header also signals the length for an extension of an FIC chunkheader, the length for an extension of an ensemble loop header, and thelength for an extension of a mobile service loop that can be generatedby a minor protocol version change.

According to an embodiment of the present invention, a receiver (orreceiving system) that can adopt the corresponding minor protocolversion change may process the corresponding extension field, whereas alegacy (or conventional) receiver that cannot adopt the correspondingminor protocol version change may skip the corresponding extension fieldby using each of the corresponding length information. For example, incase of a receiving system that can accept the corresponding minorprotocol version change, the directions given in the correspondingextension field may be known. Furthermore, the receiving system mayperform operations in accordance with the directions given in thecorresponding extension field.

According to an embodiment of the present invention, a minor protocolversion change in the FIC chunk is performed by inserting additionalfields at the respective end portion of the FIC chunk header, theensemble loop header, and the mobile service loop included in theprevious minor protocol version FIC chunk. According to an embodiment ofthe present invention, in any other case, or when the length of theadditional fields cannot be expressed (or indicated) by each extensionlength within the FIC chunk header, or when a specific field within theFIC chunk payload is missing (or cannot be found), or when the number ofbits being assigned to the corresponding field or the definition of thecorresponding field is changed (or altered), the major protocol versionof the corresponding FIC chunk is updated.

Also, the FIC chunk header signals whether the data of a correspondingFIC chink payload carry mapping information between an ensemble and amobile service within the current M/H frame, or whether the data of acorresponding FIC chink payload carry mapping information between anensemble and a mobile service within the next M/H frame. Furthermore,the FIC chunk header also signals the number of transport stream IDs ofa mobile service through which the current FIC chunk is beingtransmitted and the number of ensembles being transmitted through thecorresponding mobile service.

Accordingly, for this, the FIC chunk header may include anFIC_major_protocol_version field, an FIC_minor_protocol_version field,an FIC_chunk_header_extension_length field, anensemble_loop_header_extension_length field, anM/H_service_loop_extension_length field, a current_next_indicator field,a transport_stream_id field, and a num_ensembles field.

The FIC_major_protocol_version field corresponds to a 2-bit unsignedinteger field that represents the major version level of an FIC chunksyntax. A change in the major version level shall indicate a change in anon-backward-compatible level. When the FIC_major_protocol_version fieldis updated, legacy (or conventional) receivers, which can process theprior major protocol version of an FIC chunk protocol, shall avoidprocessing the FIC chunk.

The FIC_minor_protocol_version field corresponds to a 3-bit unsignedinteger field that represents the minor version level of an FIC chunksyntax. When it is assumed that the major version level remains thesame, a change in the minor version level shall indicate a change in abackward-compatible level. More specifically, when theFIC_minor_protocol_version field is updated, legacy (or conventional)receivers, which can process the same major version of the FIC chunkprotocol, may process a portion of the FIC chunk.

The FIC_Chunk_header_extension_length field corresponds to a 3-bitunsigned integer field identifying the length of FIC chunk headerextension bytes, which are generated by the minor protocol versionupdate of the corresponding FIC chunk. Herein, the extension bytes areappended (or added) at the end of the corresponding FIC chunk header.

The ensemble_header_extension_length field corresponds to a 3-bitunsigned integer field identifying the length of the ensemble headerextension bytes, which are generated by the minor protocol versionupdate of the corresponding FIC chunk. Herein, the extension bytes areappended (or added) at the end of the corresponding ensemble loopheader.

Also, the M/H_service_loop_extension_length field corresponds to a 4-bitunsigned integer field identifying the length of the ensemble headerextension bytes, which are generated by the minor protocol versionupdate of the M/H service loop. Herein, the extension bytes are appended(or added) at the end of the corresponding M/H service loop.

For example, it is assumed that the FIC chunk includes 2 ensembles(i.e., ensemble 0 and ensemble 1). More specifically, it is assumed thattwo mobile services are transmitted through ensemble 0, and one mobileservice is transmitted through ensemble 1. At this point, when the minorprotocol version of the FIC chunk is changed, and the FIC chunk headeris expanded by 1 byte, the FIC_chunk_header_extension_length field ismarked as ‘001’. In this case, a 1-byte expansion field (i.e.,FIC_Chunk_header_extension_bytes field) is added at the end of the FICchunk header. Also, the legacy receiver skips the 1-byte expansionfield, which is added at the end of the FIC chunk header, withoutprocessing the corresponding expansion field.

Additionally, when the ensemble loop header within the FIC chunk isexpanded by 2 bytes, the ensemble_loop_header_extension_length field ismarked as ‘010’. In this case, a 2-byte expansion field (i.e.,Ensemble_loop_header_extension_bytes field) is respectively added at theend of the ensemble 0 loop header and at the end of the ensemble 1 loopheader. Also, the legacy receiver skips the 2-byte expansion fields,which are respectively added at the end of the ensemble 0 loop headerand at the end of the ensemble 1 loop header, without processing thecorresponding 2-byte expansion fields.

Furthermore, when the mobile service loop of the FIC chunk is expandedby 1 byte, the M/H_service_loop_extension_length field is marked as‘001’. In this case, a 1-byte expansion field (i.e.,M/H_service_loop_extension_bytes field) is respectively added at the endof 2 mobile service loops being transmitted through ensemble 0 loop andat the end of 1 mobile service loop being transmitted through theensemble 1 loop. And, the legacy receiver skips the 1-byte expansionfields, which are respectively added at the end of 2 mobile serviceloops being transmitted through ensemble 0 loop and at the end of 1mobile service loop being transmitted through the ensemble 1 loop,without processing the corresponding 1-byte expansion fields.

As described above, when the FIC_minor_protocol version field ischanged, a legacy (or conventional) receiver (i.e., a receiver thatcannot adopt the minor protocol version change in the corresponding FICchunk) processes the fields apart from the extension field. Thereafter,the legacy receiver uses the FIC_chunk_header_extension_length field,the ensemble_loop_header_extension_length field, and theM/H_service_loop_extension_length field, so as to skip the correspondingexpansion fields without processing the corresponding fields. When usinga receiving system that can adopt the corresponding minor protocolversion change of the FIC chunk, each length field is used to processeven the corresponding expansion field.

The current_next_indicator field corresponds to a 1-bit indicator,which, when set to ‘1’, indicates that the corresponding FIC chunk iscurrently applicable. Alternatively, when the current_next_indicatorfield is set to ‘0’, the current_next_indicator field indicates that thecorresponding FIC chunk will be applicable for the next M/H frame.Herein, when the current_next_indicator field is set to ‘0’, the mostrecent version of the FIC chunk being transmitted with thecurrent_next_indicator field set to ‘1’ shall be currently applicable.More specifically, when the current_next_indicator field value is set to‘1’, this indicates that the corresponding FIC chunk transmits thesignaling data of the current M/H frame. Further, when thecurrent_next_indicator field value is set to ‘0’, this indicates thatthe corresponding FIC chunk transmits the signaling data of the next M/Hframe. When reconfiguration occurs, wherein the mapping informationbetween the ensemble within the current M/H frame and the mobile servicediffers from the ensemble within the next M/H frame and the mobileservice, the M/H frame prior to reconfiguration is referred to as thecurrent M/H frame, and the M/H frame following reconfiguration isreferred to as the next M/H frame.

The transport_stream_id field corresponds to a 16-bit unsigned integernumber field, which serves as a label for identifying the correspondingM/H broadcast. The value of the corresponding transport_stream_id fieldshall be equal to the value of the transport_stream_id field included inthe program association table (PAT) within the MPEG-2 transport streamof a main ATSC broadcast.

The num_ensembles field corresponds to an 8-bit unsigned integer field,which indicates the number of M/H ensembles carried through thecorresponding physical transmission channel.

FIG. 35 illustrates an exemplary syntax structure of an FIC chunkpayload according to an embodiment of the present invention.

For each ensemble corresponding to the num_ensembles field value withinthe FIC chunk header of FIG. 34, the FIC chunk payload includesconfiguration information of each ensemble and information on mobileservices being transmitted through each ensemble.

The FIC chunk payload consists of an ensemble loop and a mobile serviceloop below the ensemble loop. The FIC chunk payload enables the receiverto determine through which ensemble a requested (or desired) mobileservice is being transmitted. (This process is performed via mappingbetween the ensemble_id field and the M/H_service_id field.) Thus, thereceiver may receive RS frames belonging to the corresponding ensemble.

In order to do so, the ensemble loop of the FIC chunk payload mayinclude an ensemble_id field, an ensemble_protocol_version field, anSLT_ensemble_indicator field, a CAT_ensemble_indicator field, anMH_service_signaling_channel_version field, and a num_M/H_servicesfield, which are collectively repeated as many times as thenum_ensembles field value. The mobile service loop may include anMH_service_id field, a multi_ensemble_service field, anMH_service_status field, and an SP_indicator field, which arecollectively repeated as many times as the num_M/H_services field.

The ensemble_id field corresponds to an 8-bit unsigned integer field,which indicates a unique identifier of the corresponding ensemble. Forexample, the ensemble_id field may be assigned with values within therange ‘0x00’ to ‘0x7F’. The ensemble_id field group (or associate) themobile services with the respective ensemble. Herein, it is preferablethat the value of the ensemble_id field is derived from the parade_idfield carried (or transmitted) through the TPC data. If thecorresponding ensemble is transmitted through a primary RS frame, themost significant bit is set to ‘0’, and the remaining least significantbits are used as the parade_id field value of the corresponding parade.Meanwhile, if the corresponding ensemble is transmitted through asecondary RS frame, the most significant bit is set to ‘0’, and theremaining least significant bits are used as the parade_id field valueof the corresponding parade.

The ensemble_protocol_version field corresponds to a 5-bit field, whichspecifies a version of the corresponding ensemble structure.

The SLT_ensemble_indicator field is a 1-bit field, which indicateswhether or not the SLT is being transmitted to the service signalingchannel of the corresponding ensemble. For example, when theSLT_ensemble_indicator field value is equal to ‘1’, this may indicatethat the SLT is being transmitted to the service signaling channel. Onthe other hand, when the SLT_ensemble_indicator field value is equal to‘0’, this may indicate that the SLT is not being transmitted.

The GAT_ensemble_indicator field is also a 1-bit field, which indicateswhether or not the GAT is being transmitted to the service signalingchannel of the corresponding ensemble. For example, when theGAT_ensemble_indicator field value is equal to ‘1’, this may indicatethat the GAT is being transmitted to the service signaling channel. Onthe other hand, when the GAT_ensemble_indicator field value is equal to‘0’, this may indicate that the GAT is not being transmitted.

The MH_service_signaling_channel_version field corresponds to a 5-bitfield, which indicates a version number of the service signaling channelof the corresponding ensemble.

The num_M/H_services field corresponds to an 8-bit unsigned integerfield, which represents the number of mobile (i.e., M/H) servicescarried through the corresponding M/H ensemble.

For example, when the minor protocol version within the FIC chunk headeris changed, and when an extension field is added to the ensemble loopheader, the corresponding extension field is added immediately after thenum_M/H_services field. According to another embodiment of the presentinvention, if the num_M/H_services field is included in the mobileservice loop, the corresponding extension field that is to be added inthe ensemble loop header is added immediately after theM/H_service_configuration_version field.

The M/H_service_id field of the mobile service loop corresponds to a16-bit unsigned integer number, which identifies the corresponding M/Hservice. The value (or number) of the M/H_service_id field shall beunique within the mobile (M/H) broadcast.

The multi_ensemble_service field is a 2-bit enumerated field, whichindicates whether the corresponding mobile (M/H) service is transmittedthrough (or over) one ensemble, or whether the corresponding mobile(M/H) service is transmitted through (or over) multiple ensembles. Also,the value of the multi_ensemble_service field indicates whether or notthe mobile service is valid (or rendered meaningfully) only for themobile service portion being transmitted through (or over) thecorresponding ensemble.

The M/H_service_status field corresponds to a 2-bit enumerated field,which identifies the status of the corresponding M/H service. Forexample, the most significant bit of the M/H_service_status fieldindicates whether the corresponding M/H service is active (when set to‘1’) or inactive (when set to ‘0’). Furthermore, the least significantbit indicates whether the corresponding M/H service is hidden (when setto ‘1’) or not (when set to ‘0’).

The SP_indicator field corresponds to a 1-bit field, which, when set to‘1’, indicates whether or not service protection is applied to at leastone of the components required for providing a significant presentationof the corresponding M/H service.

For example, when the minor protocol version of the FIC chunk is change,and if an expansion field is added to the mobile service loop, theexpansion field is added after the SP_indicator field.

Also, the FIC chunk payload may include an FIC_chunk_stuffing( ) field.Stuffing of the FIC_chunk_stuffing( ) field may exist in an FIC-Chunk,to keep the boundary of the FIC-Chunk to be aligned with the boundary ofthe last FIC-Segment among FIC segments belonging to the FIC chunk. Thelength of the stuffing is determined by how much space is left afterparsing through the entire FIC-Chunk payload preceding the stuffing.

At this point, the transmitting system (not shown) according to thepresent invention divides the FIC chunk into multiple FIC segmentpayloads and forms a plurality of FIC segments by adding each FICsegment header to each FIC segment payload, thereby outputting the FICsegments to the receiving system in FIC segment units. The size of eachFIC segment unit is 37 bytes, and each FIC segment consists of a 2-byteFIC segment header and a 35-byte FIC segment payload. More specifically,an FIC chunk, which is configured of an FIC chunk header and an FICchunk payload, is segmented by units of 35 bytes. Also, an FIC segmentis configured by adding a 2-byte FIC segment header in front of eachsegmented 35-byte unit.

According to an embodiment of the present invention, the length of theFIC chunk payload is variable. Herein, the length of the FIC chunkvaries depending upon the number of ensembles being transmitted throughthe corresponding physical transmission channel and the number of mobileservices included in each ensemble.

Also, the FIC chunk payload may include stuffing data. In this case, thestuffing data are used for the boundary alignment of the FIC chunk andthe last FIC-Segment, among FIC segments belonging to the FIC chunk,according to the embodiment of the present invention. Accordingly, byminimizing the length of the stuffing data, unnecessary wasting of FICsegments can be reduced.

At this point, the number of stuffing data bytes being inserted in theFIC chunk can be calculated by using Equation 6 below.

The number of stuffing data bytes=35−jj=(5+the number of signaling data bytes being inserted in the FIC chunkpayload)mod 35  Equation 6

For example, when the added total length of the 5-byte header within theFIC chunk and signaling data, which is to be inserted in the payloadwithin the FIC chunk, is equal to 205 bytes, the payload of the FICchunk may include 5 bytes of stuffing data because j is equal to 30 inEquation 6. Also, the length of the FIC chunk payload including thestuffing data is equal to 210 bytes. Thereafter, the FIC chunk isdivided into 6 FIC segments, which are then transmitted. At this point,a segment number is sequentially assigned to each of the 6 FIC segmentsdivided from the FIC chunk.

Furthermore, the present invention may transmit the FIC segments dividedfrom a single FIC chunk to a single sub-frame, or may transmit thedivided FIC segments to multiple sub-frames. If the FIC chunk is dividedand transmitted to multiple sub-frames, signaling data, which arerequired even when the amount of data that are to be transmitted throughthe FIC chunk is larger than the amount of FIC segments beingtransmitted through a single sub-frame (this case corresponds to whenmultiple services having very low bit rates are being executed), may allbe transmitted through the FIC chunk.

Herein, the FIC segment numbers represent FIC segment numbers withineach FIC chunk, and not the FIC segment number within each sub-frame.Thus, the subordinate relation between the FIC chunk and the sub-framecan be eliminated, thereby reducing excessive waste of FIC segments.

Furthermore, the present invention may add a null FIC segment. Despitethe repeated transmission of the FIC chunk, and when stuffing isrequired in the corresponding M/H frame, the null FIC segment is usedfor the purpose of processing the remaining FIC segments. For example,it is assumed that TNoG is equal to ‘3’ and that the FIC chunk isdivided into 2 FIC segments. Herein, when the FIC chunk is repeatedlytransmitted through 5 sub-frames within a single M/H frame, only 2 FICsegments are transmitted through one of the 5 sub-frames (e.g., thesub-frame chronologically placed in the last order). In this case, onenull FIC segment is assigned to the corresponding sub-frame, therebybeing transmitted. More specifically, the null FIC segment is used foraligning the boundary of the FIC chunk and the boundary of the M/Hframe. At this point, since the null FIC segment is not an FIC segmentdivided from the FIC chunk, an FIC segment number is not assigned to thenull FIC segment.

In the present invention, when a single FIC chunk is divided into aplurality of FIC segments, and when the divided FIC segments areincluded in each data group of at least one sub-frame within the M/Hframe, so as to be transmitted, the corresponding FIC segments areallocated in a reversed order starting from the last sub-frame withinthe corresponding M/H frame. According to an embodiment of the presentinvention, in case a null FIC segment exists, the null FIC segment ispositioned in the sub-frame within the M/H frame, so that thecorresponding null FIC segment can be transmitted as the last (or final)segment.

At this point, in order to enable the receiving system to discard thenull FIC segment without having to process the corresponding null FICsegment, identification information that can identify (or distinguish)the null FIC segment is required.

According to an embodiment of the present invention, the presentinvention uses the FIC_segment_type field within the header of the nullFIC segment as the identification information for identifying the nullFIC segment. In this embodiment, the value of the FIC_segment_type fieldwithin the null FIC segment header is set to ‘11’, so as to identify thecorresponding null FIC segment. More specifically, when theFIC_segment_type field value within the null FIC segment header is setto ‘11’ and transmitted to the receiving system, the receiving systemmay discard the payload of the FIC segment having the FIC_segment_typefield value set to ‘11’ without having to process the corresponding FICsegment payload. Herein, the value ‘11’ is merely an exemplary valuegiven to facilitate and simplify the understanding of the presentinvention. As long as a pre-arrangement between the receiving system andthe transmitting system is established, any value that can identify thenull FIC segment may be given to the FIC_segment_type field. Therefore,the present invention will not be limited only to the example setpresented herein. Furthermore, the identification information that canidentify the null FIC segment may also be indicated by using anotherfield within the FIC segment header.

FIG. 36 illustrates an exemplary syntax structure of an FIC segmentheader according to an embodiment of the present invention.

Herein, the FIC segment header may include an FIC_segment_type field, anFIC_chunk_major_protocol_version field, a current_next_indicator field,an error_indicator field, an FIC_segment_num field, and anFIC_last_segment_num field. Each field will now be described as follows.

The FIC_segment_type field corresponds to a 2-bit field, which, when setto ‘00’ indicates that the corresponding FIC segment is carrying aportion of an FIC chunk. Alternatively, when the FIC_segment_type fieldis set to ‘11’, the FIC_segment_type field indicates that thecorresponding FIC segment is a null FIC segment, which transmitsstuffing data. Herein, the remaining values are reserved for future use.

The FIC_Chunk_major_protocol_version field corresponds to a 2-bit field,which indicates a major protocol version of the corresponding FIC chunk.At this point, the value of the FIC_Chunk_major_protocol_version fieldshould be the same as the value of the FIC_major_protocol_version fieldwithin the corresponding FIC chunk header. Since reference may be madeto the description of the FIC chunk header shown in FIG. 34, a detaileddescription of the major protocol version of the FIC chunk syntax willbe omitted for simplicity.

The current_next_indicator field corresponds to a 1-bit indicator,which, when set to ‘1’, shall indicate that the corresponding FICsegment is carrying a portion of the FIC chunk, which is applicable tothe current M/H frame. Alternatively, when the value of thecurrent_next_indicator field is set to ‘0’, the current_next_indicatorfield shall indicate that the corresponding FIC segment is carrying aportion of the FIC chunk, which will be applicable for the next M/Hframe.

The error_indicator field corresponds to a 1-bit field, which indicateswhether or not an error has occurred in the corresponding FTC segmentduring transmission. Herein, the error_indicator field is set to ‘1’,when an error has occurred. And, the error_indicator field is set to‘0’, when an error does not exist (or has not occurred). Morespecifically, during the process of configuring the FIC segment, when anon-recovered error exists, the error_indicator field is set to ‘1’.More specifically, the error_indicator field enables the receivingsystem to recognize the existence (or presence) of an error within thecorresponding FIC segment.

The FIC_segment_num field corresponds to a 4-bit unsigned integer numberfield, which indicates a number of the corresponding FIC segment. Forexample, if the corresponding FIC segment is the first FIC segment ofthe FIC chunk, the value of the FIC_segment_num field shall be set to‘0x0’. Also, if the corresponding FIC segment is the second FIC segmentof the FIC chunk, the value of the FIC_segment_num field shall be set to‘0x1’. More specifically, the FIC_segment_num field shall be incrementedby one with each additional FIC segment in the FIC chunk. Herein, if theFIC chunk is divided into 4 FIC segments, the FIC_segment_num fieldvalue of the last FIC segment within the FIC chunk will be indicated as‘0x3’.

The FIC_last_segment_num field corresponds to a 4-bit unsigned integernumber field, which indicates the number of the last FIC segment (i.e.,the FIC segment having the highest FIC_segment_num field value) within acomplete FIC chunk.

In the conventional method, FIC segment numbers are sequentiallyassigned (or allocated) for each FIC segment within one sub-frame.Therefore, in this case, the last FIC segment number always matches withthe TNoG (i.e., the last FIC segment number is always equal to theTNoG). However, when using the FIC number assignment method according tothe present invention, the last FIC segment number may not always matchwith the TNoG. More specifically, the last FIC segment number may matchwith the TNoG, or the last FIC segment number may not match with theTNoG. The TNoG represents a total number of data groups that areallocated (or assigned) to a single sub-frame. For example, when theTNoG is equal to ‘6’, and when the FIC chunk is divided into 8 FICsegments, the TNoG is equal to ‘6’, and the last FIC segment number is‘8’.

According to another embodiment of the present invention, the null FICsegment may be identified by using the value of the FIC_segment_numfield within the FIC segment header. More specifically, since an FICsegment number is not assigned to the null FIC segment, the transmittingsystem allocates null data to the FIC_segment_num field value of thenull FIC segment, and the receiving system may allow the FIC segmenthaving null data assigned to the FIC_segment_num field value to berecognized as the null FIC segment. Herein, instead of the null data,data pre-arranged by the receiving system and the transmitting systemmay be assigned to the FIC_segment_num field value, instead of the nulldata.

As described above, the FIC chunk is divided into a plurality of FICsegments, thereby being transmitted through a single sub-frame or beingtransmitted through multiple sub-frames. Also, FIC segments divided froma single FIC chunk may be transmitted through a single sub-frame, or FICsegments divided from multiple single FIC chunks may be transmittedthrough a single sub-frame. At this point, the number assigned to eachFIC segment corresponds to a number within the corresponding FIC chunk(i.e., the FIC_seg_number value), and not the number within thecorresponding sub-frame. Also, the null FIC segment may be transmittedfor aligning the boundary of the M/H frame and the boundary of the FICchunk. At this point, an FIC segment number is not assigned to the nullFIC segment.

As described above, one FIC chunk may be transmitted through multiplesub-frames, or multiple FIC chunks may be transmitted through a singlesub-frame. However, according to the embodiment of the presentinvention, the FIC segments are interleaved and transmitted in sub-frameunits.

Meanwhile, FIG. 37 illustrates an exemplary structure of a bit streamsyntax of an SMT section which is included in the RS frame and thentransmitted. Herein, the SMT section is configured in an MPEG-2 privatesection format for simplicity. However, the SMT section data may beconfigured in any possible format.

The SMT may provide access information of mobile services within anensemble including the SMT. Also, the SMT may provide informationrequired for the rendering of mobile services. Furthermore, the SMT mayinclude at least one or more descriptors. Herein, other additional (orsupplementary) information may be described by the descriptor.

At this point, the service signaling channel that transmits the SMT mayfurther include another signaling table (e.g., GAT) in addition to theSMT.

Herein, according to the embodiment of the present invention, IPdatagrams of the service signaling channel have the same well-knowndestination IP address and the same well-known destination UDP portnumber. Therefore, the SMT included in the service signaling data isdistinguished (or identified) by a table identifier. More specifically,the table identifier may correspond to a table_id existing in thecorresponding table or in a header of the corresponding table section.And, when required, the table identifier may further refer to atable_id_extension field, so as to perform the identification process.Exemplary fields that can be transmitted through the SMT section willnow be described in detail.

A table_id field is an 8-bit table identifier, which may be set up as anidentifier for identifying the SMT.

A section_syntax_indicator field corresponds to an indicator definingthe section format of the SMT. For example, the section_syntax_indicatorfield shall be set to ‘0’ to always indicate that this table is derivedfrom the “short” form of the MPEG-2 private section table format maycorrespond to MPEG long-form syntax.

A private_indicator field is a 1-bit field, which indicates whether ornot the SMT follows (or is in accordance with) a private section.

A section_length field is a 12-bit field, which specifies the sectionlength of the remaining SMT data bytes immediately following thesection_length field.

A table_id_extension field corresponds to a table-dependent 16-bitfield. Herein, the table_id_extension field corresponds to a logicalportion of the table_id field providing the scope for the remainingfields. The table_id_extension field includes a SMT_protocol_versionfield and an ensemble_id field.

The SMT_protocol_version field corresponds to an 8-bit unsigned integerfield. Herein, the SMT_protocol_version field indicates a protocolversion for allowing the corresponding SMT to carry, in a futureprocess, parameters that may be structure differently from those definedin the current protocol. Presently, the value of theSMT_protocol_version field shall be equal to zero (0). Non-zero valuesof the SMT_protocol_version field may be used by a future version ofthis standard to indicate structurally different tables.

The ensemble_id field corresponds to an 8-bit field. Herein, the IDvalues associated with the corresponding ensemble that can be assignedto the ensemble_id field may range from ‘0x00’ and ‘0x3F’. It ispreferable that the value of the ensemble_id field is derived from theTPC data of the parade_id field. When the corresponding ensemble istransmitted through a primary RS frame, the most significant bit (MSB)is set to ‘0’, and the remaining 7 bits are used as the parade_id fieldvalue of the corresponding parade. Meanwhile, when the correspondingensemble is transmitted through a primary RS frame, the most significantbit (MSB) is set to ‘1’, and the remaining 7 bits are used as theparade_id field value of the corresponding parade.

A version_number field corresponds to a 5-bit field, which specifies theversion number of the SMT.

A current_next_indicator field corresponds to a 1-bit field indicatingwhether or not the SMT section is currently applicable.

A section_number field is an 8-bit field specifying the number of thecurrent SMT section.

A last_section_number field corresponds to an 8-bit field that specifiesthe number of the last section configuring the corresponding SMT.

And, a num_MH_services field corresponds to an 8-bit field, whichspecifies the number of mobile services in the corresponding SMTsection.

Hereinafter, a number of ‘for’ loop (also referred to as mobile (M/H)service loop) statements equivalent to the number of mobile servicescorresponding to the num_MH_services field is performed so as to providesignaling information on multiple mobile services. More specifically,signaling information of the corresponding mobile service is indicatedfor each mobile service that is included in the SMT section. Herein, thefollowing field information corresponding to each mobile service may beprovided as described below.

An MH_service_id field corresponds to a 16-bit unsigned integer number,which can uniquely identify the corresponding mobile service within thescope of the corresponding SMT section.

A multi_ensemble_service field corresponds to a 2-bit field, whichindicates whether the corresponding mobile service is transmittedthrough one or more ensembles. Since the multi_ensemble_service fieldhas the same meaning as the multi_ensemble_service field included in theFIC chunk, detailed description of the same will be omitted forsimplicity.

An MH_service_status field corresponds to a 2-bit field, which canidentify the status of the corresponding mobile service. Herein, the MSBindicates whether the corresponding mobile service is active (‘1’) orwhether the corresponding mobile service is inactive (‘0’). Also, theLSB indicates whether the corresponding mobile service is hidden (‘1’)or not hidden (‘0’).

An SP_indicator field corresponds to a 1-bit field, which specifiesservice protection status of the corresponding mobile service. If theSP_indicator field is set to ‘1’, then service protection is applied toat least one of the components needed to provide a meaningfulpresentation of the corresponding service.

A short_MH_service_name_length field corresponds to a 3-bit field, whichindicates the length of a short service name described in ashort_service_name field in byte-length units.

The short_MH_service_name field indicates the short name of thecorresponding mobile service.

An MH_service_category field is a 6-bit field, which identifies the typecategory of the corresponding mobile service.

A num_components field corresponds to a 5-bit field, which specifies thenumber of IP stream components in the corresponding mobile service.

An IP_version_flag field corresponds to a 1-bit indicator, which whenset to ‘0’ indicates that a source_IP_address field, anMH_service_destination_IP_address field, and acomponent_destination_IP_address field correspond to IPv4 addresses. Thevalue of ‘1’ for the IP_version_flag field is reserved for any possiblefuture indication that the source_IP_address field, theMH_service_destination_IP_address field, and thecomponent_destination_IP_address field correspond to IPv6 addresses.However, the usage of IPv6 addressing is currently undefined.

A source_IP_address_flag corresponds to a 1-bit Boolean flag, whichindicates, when set, that a source IP address value for thecorresponding service exists (or is present) so as to indicate a sourcespecific multicast.

An MH_service_destination_IP_address_flag corresponds to a 1-bit, whichindicates, when set, that the corresponding IP stream component istransmitted through an IP datagram having a destination IP addressdifferent from that of the MH_service_destination_IP_address field.Therefore, when the MH_service_destination_IP_address_flag is set, thereceiving system may use the component_destination_IP_address as thedestination_IP_address in order to access the corresponding IP streamcomponent. Furthermore, the receiving system ignores (or disregards) theMH_service_destination_IP_address field within the mobile service loop.

The source_IP_address field corresponds to a 32-bit field or a 128-bitfield. When the source_IP_address_flag is set to ‘1’, thesource_IP_address field is required to be interpreted (or analyzed).However, when the source_IP_address_flag is set to ‘0’, thesource_IP_address field is not required to be interpreted (or analyzed).When the source_IP_address_flag is set to ‘1’, and when theIP_version_flag field is set to ‘0’, the corresponding field indicatesthat the source_IP_address field indicates a 32-bit IPv4 addressspecifying the corresponding mobile service source. Alternatively, ifthe IP_version_flag field is set to ‘1’, the source_IP_address fieldindicates a 32-bit IPv6 address specifying the corresponding mobileservice source.

The MH_service_destination_IP_address field corresponds to a 32-bitfield or a 128-bit field. When theMH_service_destination_IP_address_flag field is set to ‘1’, theMH_service_destination_IP_address_flag is required to be interpreted (oranalyzed). However, when the MH_service_destination_IP_address_flag isset to ‘0’, the MH_service_destination_IP_address_flag is not requiredto be interpreted (or analyzed). Herein, if theMH_service_destination_IP_address_flag is set to ‘1’, and if theIP_version_flag field is set to ‘0’, theMH_service_destination_IP_address field indicates a 32-bit destinationIPv4 address for the corresponding mobile service. Alternatively, if theMH_service_destination_IP_address_flag is set to ‘1’, and if theIP_version_flag field is set to ‘1’, theMH_service_destination_IP_address field indicates a 64-bit destinationIPv6 address for the corresponding mobile service. In case thecorresponding MH_service_destination_IP_address field cannot beinterpreted, the component_destination_IP_address field within acomponent loop shall be interpreted. And, in this case, the receivingsystem shall use the component_destination_IP_address in order to accessthe IP stream component.

Meanwhile, the SMT according to the embodiment of the present inventionprovides information on multiple components using the ‘for’ loopstatement.

Hereinafter, a number of ‘for’ loop (also referred to as component loop)statements equivalent to the number of components corresponding to thenum_component field value is performed so as to provide accessinformation on multiple components. More specifically, accessinformation of each component included in the corresponding mobileservice is provided. In this case, the following field information oneach component may be provided as described below.

A component_source_IP_address_flag field is a 1-bit field (or a 1-bitBoolean flag), which indicates, when set to ‘1’, that thecomponent_source_IP_address field is present for this component.

More specifically, a mobile service may include diverse types ofcomponents, for example, a mobile service may include an audiocomponent, or a mobile service may include a video component, or amobile service may include a FLUTE component.

At this point, when the component_source_IP_address_flag field is set to‘1’, this signifies that the component_source_IP_address field exists,and this field indicates a source IP address of an IP datagram carryingthe corresponding component.

For example, when the component_source_IP_address_flag field of theFLUTE component is set to ‘1’, the component_source_IP_address fieldindicates the source IP address of the IP datagram carrying the FLUTEcomponent.

According to an embodiment of the present invention, in case aservice_source_IP_address field within a mobile service loop and acomponent_source_IP_address within a component loop both exist, yet ifthe field values are different from one another, the source IP addressof the IP datagram of the corresponding component is acquired from thecomponent_source_IP_address field. More specifically, theservice_source_IP_address field within the mobile service loop isdisregarded.

According to another embodiment of the present invention, in case theservice_source_IP_address field exists and thecomponent_source_IP_address field does not exist, the source IP addressof the IP datagram of the corresponding component is acquired from theservice_source_IP_address field. And, in the opposite case, i.e., incase the service_source_IP_address field does not exists and thecomponent_source_IP_address field exists, the source IP address of theIP datagram of the corresponding component is acquired from thecomponent_source_IP_address field.

As described above, in the present invention, thecomponent_source_IP_address field exists when thecomponent_source_IP_address_flag field value is equal to ‘1’. And,according to an embodiment of the present invention, when thecomponent_source_IP_address field exists, the source IP address of theIP datagram of the corresponding component is identical to thecomponent_source_IP_address field value. And, according to anotherembodiment of the present invention, in case thecomponent_source_IP_address field does not exist, the source IP addressof the IP datagram of the corresponding component is identical to theservice_source_IP_address field value.

And, according to another embodiment of the present invention, in casethe service_source_IP_address field and the component_source_IP_addressfield do not exist, the source IP address is not used when acquiring theIP datagram of the corresponding component.

An essential_component_indicator field is a 1-bit field, which indicatesthat the corresponding component is an essential component for themobile service, when the essential_component_indicator field value isset to ‘1’. Otherwise, the essential_component_indicator field indicatesthat the corresponding component is an optional component. For example,in case of a basic layer audio stream and video stream, theessential_component_indicator field value is set to ‘1’. And, in case ofthe enhanced layer video stream, the essential_component_indicator fieldvalue is set to ‘0’.

A component_destination_IP_address_flag field corresponds to a 1-bitBoolean flag. When the component_destination_IP_address_flag field isset to ‘1’, this indicates that a component_destination_IP_addressexists for the corresponding component.

A port_num_count field corresponds to a 6-bit field, which indicates aUDP port number associated with the corresponding UDP/IP streamcomponent. Herein, the destination UDP Port number value is increased by1 starting from a destination_UDP_port_num field value. Thedestination_UDP_port_num field corresponds to a 16-bit field, whichindicates a destination UDP port number for the corresponding IP streamcomponent.

A component_source_IP_address field corresponds to a 32-bit or 128-bitfield, which exists when the value of thecomponent_source_IP_address_flag field is equal to ‘1’. At this point,in case the IP_version_flag field is set to ‘0’, thecomponent_source_IP_address field indicates a 32-bit source IPv4 addressfor the corresponding IP stream component. Also, in case theIP_version_flag field is set to ‘1’, the component_source_IP_addressfield indicates a 128-bit source IPv6 address for the corresponding IPstream component.

According to an embodiment of the present invention, in case thecomponent_source_IP_address field exists, the source IP address of an IPdatagram of the corresponding component is acquired from thecomponent_source_IP_address field.

A component_destination_IP_address field corresponds to a 32-bit fieldor a 128-bit field. When the IPversion_flag field is set to ‘0’, thecomponent_destination_IP_address field indicates a 32-bit destinationIPv4 address for the corresponding IP stream component.

Furthermore, when the IP_version_flag field is set to ‘1’, thecomponent_destination_IP_address field indicates a 128-bit destinationIPv6 address for the corresponding IP stream component. When this fieldis present, the destination address of the IP datagrams carrying thecorresponding component of the M/H service shall match the address inthe component_destination_IP_address field. Alternatively, when thisfield is not present, the destination address of the IP datagramscarrying the corresponding component shall match the address in theM/H_service_destination_IP_address field. The conditional use of the 128bit-long address version of this field is to facilitate possible futureusage of the IPv6, although the usage of the IPv6 is currentlyundefined.

A num_component_level_descriptors field corresponds to a 4-bit field,indicating a number of descriptors providing additional information onthe component level.

A number of component_level_descriptor( ) corresponding to the value ofthe num_component_level_descriptors field is included in the componentloop, so as to provide additional (or supplemental) information on thecorresponding component.

A num_MH_service_level_descriptors field corresponds to a 4-bit fieldindicating a number of descriptors providing additional information ofthe corresponding mobile service level.

A number of service_level_descriptor( ) corresponding to the value ofthe num_MH_service_level_descriptors field is included in the mobileservice loop, so as to provide additional (or supplemental) informationon the mobile service.

A num_ensemble_level_descriptors field corresponds to a 4-bit field,which indicates a number of descriptors providing additional informationon ensemble levels.

Furthermore, a number of ensemble_level_descriptor( ) corresponding tothe value of the num_ensemble_level_descriptors field is included in theensemble loop, so as to provide additional (or supplemental) informationon the ensemble.

FIG. 38 illustrates an embodiment of a bit stream syntax structure of acomponent_level_descriptors( ). The component_descriptor( ) is used asone of the component level descriptor component_level_descriptors( ) ofthe NST and describes additional signaling information of thecorresponding component.

The following is a description of each field of thecomponent_descriptor( ).

In FIG. 38, a descriptor_tag field (8-bit) is a descriptor identifierand it can be set as an identifier that identifies thecomponent_descriptor( ).

A descriptor_length field (8-bit) describes the remaining length of thedescriptor starting after the descriptor_length field and to the end ofthis descriptor, in bytes.

A component_type field (7-bit) shall identify the encoding format of thecomponent. The value may be any of the values assigned by TANA for thepayload_type of an RTP/AVP stream, or it may be any of the valuesassigned by ATSC, or it may be a “dynamic value” in the range 96-127.For components consisting of media carried via RTP, the value of thisfield shall match the value in the payload_type field in the RTP headerof the IP stream carrying this component. Note that additional values ofthe component_type field in the range of 43-71 can be defined in futureversions of this standard.

A component_encryption_flag (1-bit) informs whether the correspondingcomponent is encrypted or not.

A Num_STKM_streams field (8-bit) indicates the number STKM streams ifcomponent_encryption_flag has been encrypted. (The num_STKM_streamsfield (8-bit) is an 8-bit unsigned integer field that shall identify thenumber of STKM streams associated with this component.

A STKM_stream_id field (8-bit) is repeated as much as the field value ofNum_STKM_streams and indicates a value that identifies a SKTM streamthat can acquire a key required for decryption.

A component_data (component_type) element provides the encodingparameters and/or other parameters necessary for rendering thiscomponent. The structure of the component_data is determined by thevalue of component_type field.

For example, if the component_type field value is 35 then component_data(component_type) field provides component data for H.264/AVC videostream.

In another example, if the component_type field value is 38 thencomponent_data (component_type) field provides data for FLUTE filedelivery.

One mobile service can be included in multiple FLUTE sessions. Thus, onemobile service may be configured with plurality of FLUTE sessions. EachFLUTE session may be signaled using component_data( ).

Meanwhile, according to another embodiment of the present invention, abroadcast receiver to provide a user with a mobile broadcast service byprocessing a mobile broadcast signal provided over a mobile broadcastnetwork, particularly the M/H broadcast network is allowed to providedisaster broadcasting (or disaster alert). To provide the disasterbroadcast containing disaster information, signaling information for thedisaster broadcast is necessary. Hereinafter, a description will begiven of various examples of a method for signaling the signalinginformation for the disaster broadcast.

The signaling information may be signaled to the FIC chunk and/or theSMT. At this time, the signaling information signaled to the FIC chunkand the signaling information signaled to the SMT may be different from,or identical to each other, or parts thereof may duplicate.

In addition, the present invention defines a new table. The signalinginformation for disaster broadcast may be signaled to this table. Thistable will be referred to as an Emergency Alert Table (EAT).

Hereinafter, a description will be given of signaling information forthe disaster broadcast using an FIC chunk. The disaster broadcast may bea specific channel or a text indicating the disaster status. In thisembodiment, a message containing text-type disaster information forinforming the disaster status is referred to as an emergency alertmessage for simplicity of description.

As an example, the signaling information signaled to the FIC chunkcontains at least one of emergency alert system (EAS) indicationinformation (or referred to as an EAS indicator field) for informing thecurrent mobile broadcast of existence of an emergency alert message andwake-up indication information (or referred to as a wake-up indicatorfield) for supporting a wake-up function.

The EAS indication information informs of existence of an emergencyalert message in the current mobile broadcast.

The wake-up indication information informs of whether the emergencyalert message needs the wake-up function. That is, the wake-upindication information is needed to support the wake-up function of thebroadcast receiver in issuing a disaster alert.

Herein, the wake-up function refers to a function for compulsorilyswitching the broadcast receiver to the active mode broadcast receivereven if the broadcast receiver is in the sleep mode (or referred to asthe standby mode when a serious emergency alert message requiring switchto the active mode is issued. To support the wake-up function, thebroadcast receiver needs to consistently watch broadcast signals even inthe sleep mode and to recognize how urgent the disaster alert is asquickly as possible.

The FIC chunk is configured with an FIC chunk header and an FIC chunkpayload, and the FIC chunk is divided into a plurality of FIC segmentpayloads. When the FIC segment header is added to each of the FICsegment payloads, one FIC segment is constructed. The FIC segment istransmitted through one data group. That is, the FIC segment is thesmallest unit of transmission at the physical layer.

FIG. 39 illustrates another embodiment of the syntax structure of theFIC segment header to which the EAS indication information and thewake-up indication information are signaled. Details of the FIC segmentheader of FIG. 39 are the same as those of the FIC segment header ofFIG. 36 except that the FIC segment header of FIG. 39 allocates thewake-up indicator field and the EAS indicator field using the tworeserved bits of FIG. 36. Accordingly, a description of the fields ofFIG. 39 identical to those of FIG. 36 will be omitted.

In FIG. 39, the wake-up indicator field has, for example, 1 bitallocated thereto, and indicates wake-up. The broadcast receiverdetermines whether to switch to the active mode according to the valueof the wake-up indicator field.

In addition, the EAS indicator field has, for example, 1 bit allocatedthereto, and indicates existence of an emergency alert message in thecurrent mobile broadcast.

By adding the EAS indicator field to the FIC segment header as describedabove, the broadcast receiver may quickly sense whether an emergencyalert message is included in the current broadcast service.

FIG. 40 illustrates another embodiment of the syntax structure of theFIC segment header to which the EAS indication information and thewake-up indication information are signaled. Details of the FIC segmentheader of FIG. 40 are the same as those of the FIC segment header ofFIG. 36 except that the FIC segment header of FIG. 40 allocates thewake-up indicator field using the two reserved bits of FIG. 36.Accordingly, a description of the fields of FIG. 39 identical to thoseof FIG. 36 will be omitted.

That is, in FIG. 40, the wake-up indicator field has, for example, 2bits allocated thereto, and indicates wake-up. The broadcast receiverdetermines whether to switch to the active mode according to the valueof the wake-up indicator field when an emergency alert message isissued.

FIG. 41 shows an example of meanings allocated to the values of the 2bit wake-up indicator field. For example, when the value of the wake-upindicator field is 01, the wake-up function may be enabled. When 10, thewake-up function may be disabled. For example, when the value of thewake-up indicator field is 01, and the current mode is the sleep mode,the broadcast receiver switches to the active mode.

The opposite case is also possible. That is, when the value of thewake-up indicator field is 01, the wake-up function may be disabled.When 10, the wake-up function may be enabled. In the case that 1 bit isallocated to the wake-up indicator field, the wake-up function may beturned on/off using the 1 bit. Since this is an item selected by thedesigner, embodiments of the present invention are not limited to theabove example.

While the wake-up indicator of FIG. 39 is provided with 1 bit allocatedthereto, the wake-up indicator of FIG. 40 has 2 bits allocated toindicate wake-up.

In the case that the wake-up indicator field is allocated as shown inFIG. 40, the EAS indication information is allocated, for example, usingthe reserved bits of the FIC chunk payload.

FIG. 42 illustrates an embodiment of the syntax structure of the FICchunk payload to which the EAS indication information is signaled.Details of the FIC chunk payload of FIG. 42 are the same as those of theFIC chunk payload of FIG. 35 except that the EAS indicator field isallocated using the reserved bit. Accordingly, a description of thefields of FIG. 42 identical to those of FIG. 35 will be omitted.

That is, in FIG. 42, 1 bit is allocated to the ensemble loop for the EASindicator field (EAS_ensemble_indicator). This field indicates existenceof an emergency alert message in the current broadcast.

For example, when the value of the EAS indicator field is 1, an ensembleidentified by the ensemble identifier in the ensemble loop may be set toindicate that an emergency alert message has been received. The oppositecase is also possible. That is, when the value of the EAS indicatorfield is 0, the ensemble may be set to indicate that the emergency alertmessage has been received. Since this is an item selected by thedesigner, embodiments of the present invention are not limited to theabove example.

In performing wake-up, the broadcast receiver needs to specify anensemble frequency (or a base band) at which an emergency alert messagecan be received. To this end, the EAS indicator field is needed.

That is, informing existence of an emergency alert message using the FICsegment header is the most efficient method for the wake-up function andquick acquisition of an emergency alert message in the broadcastreceiver. However, if the FIC segment is the basic unit for creation ofan FIC chunk, and the broadcast receiver does not respond to the changeof reserved bits of the FIC segment header, existence of an emergencyalert message in the current mobile broadcast cannot be recognized oncethe FIC chunks are collected. Accordingly, in this embodiment, byallocating the EAS indicator field to the FIC chunk payload, thebroadcast receiver is allowed to notice whether an emergency alertmessage exists in the current ensemble immediately after the FIC chunksare collected.

In addition, in the case that the broadcast receiver is not in theactive mode, the broadcast receiver is allowed to receive an emergencyalert message with the minimum energy maintained by signaling wake-upinformation to the TPC of the smallest unit for signaling.

The wake-up information includes, for example, wake-up indicationinformation. The wake-up information may further include wake-up versioninformation.

For example, 1 bit of the wake-up indication information and 5 bits ofthe wake-up version information are signaled using the reserved bits inthe syntax of the TPC data of FIG. 31.

Since the wake-up indication information (wake_up_indicator) has beendescribed in detail in the description of the FIC, a detaileddescription thereof will be omitted. For example, if the value of thewake_up_indicator field is 0, and the broadcast receiver is in the sleepmode (or standby mode), the broadcast receiver is compulsorily switchedto the active mode. If the value of the field is 1, the broadcastreceiver maintains the current mode. That is, in the sleep mode, thereceiver is allowed to continue monitoring the TPC. In the case that thereceiver is providing the mobile broadcast service, it is allowed tokeep providing the mobile broadcast service.

The wake-up version information (wake_up_version_number) indicates theversion number of wake-up signaling. The receiver may compare thewake-up version numbers to determine whether the information is newwake-up information before switching from the sleep mode to the activemode to receive the FIC.

By signaling the wake-up information to the TPC data, the broadcastreceiver is allowed to determine whether to perform the wake-up functionbased on the TPC data, namely, whether to compulsorily switch from thecurrent mode to the active mode. In addition, by signaling the wake-upinformation to the TPC data, the broadcast receiver is allowed tocompulsorily perform the wake-up function to receive disaster alert overmobile broadcast even when failing to receive signaling informationrelated to the disaster alert. Particularly, by signaling the wake-upinformation to the TPC data, the broadcast receiver is allowed toreceive disaster information with the minimum consumption of the batteryeven in a mode other than the active mode.

Meanwhile, an emergency alert message containing disaster information(or content) may be transmitted in various forms. For example, theemergency alert message may be transmitted in the form of a CAP messageor syntax.

Herein, the common alerting protocol (CAP) message is an emergency alertmessage of a common format created by authoring authorities forgeneration of a disaster alert. A CAP message generated as above isdelivered to various disaster systems including a commercial mobilealert system (CMAS) over the Open Platform for Emergency Networks(OPEN), which is an integrated network for delivery of emergency alertmessages. Each disaster alert system processes a CAP message for its ownpurpose and use, thereby providing a corresponding disaster alertservice. For example, the CMAS selects a message proper for a providernetwork among delivered emergency messages and extracts a text in 90words or less from the message, thereby providing a disaster service inthe form of a text message.

In an embodiment, the CAP message is carried in a descriptor and thedescriptor is included in the SMT. The descriptor containing the CAPmessage will be referred to as an EAS message descriptor(EAS_Message_descriptor( )). When the EAS descriptor is transmitted, itmay be contained in the ensemble level or the service level of the SMT.

FIG. 43 illustrates the syntax structure of the EAS message descriptoraccording to one embodiment of the present invention.

In FIG. 43, the descriptor_tag field (8 bits) is a descriptoridentifier. An identifier (or a tag value) to identify whether adescriptor is the EAS message descriptor is allocated.

The descriptor_length field (8 bits) indicates the remaining length ofthis descriptor from the descriptor_length field to the end of thedescriptor in unit of byte.

The Length_of_CAP field (8 bits) indicates the length of a CAP messagetransmitted in the multiple string structure.

The CAP message in the multiple string structure is transmitted byrepeating the CAP field by the value of the Length_of_CAP field. At thistime, a separate EAS syntax may be transmitted in place of the CAPmessage.

FIG. 44 illustrates the syntax structure of the EAS message descriptoraccording to another embodiment of the present invention.

In FIG. 44, the descriptor_tag field (8 bits) is a descriptoridentifier, and an identifier (or a tag value) to identify whether adescriptor is the EAS message descriptor is allocated to this field.

The descriptor_length field (8 bits) indicates the remaining length ofthis descriptor from the descriptor_length field to the end of thedescriptor in the unit of byte.

The CAP_version_number field (4 bits) indicates the version informationof a CAP message. For example, when the CAP message changes, the valueof the CAP_version_number field increases. Accordingly, the broadcastreceiver is allowed to determine whether the CAP messages are repeatedusing this field value. That is, since the CAP message is emergencyinformation, the same content may be periodically transmitted. In thiscase, every time a CAP message is received, the broadcast receiver candetermine whether the received message is a change of the previouslyreceived message or new information, using the value of theCAP_version_number field.

The EAS_NRT_included_flag field (1 bit) indicates whether a non-realtime (NRT) service related to a current disaster broadcast service (oremergency alert message) exists.

If the EAS_NRT_included_flag field indicates existence of an NRT servicerelated to the current disaster broadcast, an EAS NRT loop including theessential_content_linkage field and num_associated_service field exists.

The essential_content_linkage field (8 bits) indicates the value oflinkage between a file (or a content item) sent in NRT and the content(or a content item) in the ESG. For example, if the value of theessential_content_linkage field is 0, the user interface (UI) displays alist of NRT services for the EAS. If the value is not 0, the UE displaysa file having the value of the essential_content_linkage field as thevalue of content_linkage on the screen. This means that the contentcontained in the file provided in NRT is highly associated with adisaster broadcast (or emergency alert message).

The num_associated_service field (4 bits) indicates the number ofservices associated with the current disaster broadcast and transmittedin NRT. An identifier of each of the associated services is indicated byrepeating the associated_service_id field (16 bit) by the value of thenum_associated_service field.

The CAP_message_type field (1 bit) indicates whether an emergency alertmessage is transmitted in the CAP message structure on syntax structure.

The length_of_CAP_message_id field (7 bits) indicates the length of thetext of the CAP message identifier (ID).

The CAP_message_id field (variable) indicates the CAP message identifierin a text.

The length_of_CAP field (16 bit) indicates the length of the CAPmessage.

The CAP field (variable) contains a CAP message or EAS syntax.

Since the same content of the EAS message descriptor shown in FIG. 43 or44 should be broadcasted in all broadcasts, and therefore the EASmessage descriptor may be included in at least one of the ensemble leveland service level of the SMT. The SMT is essentially included in allensembles of a channel. That is, the EAS message descriptor may betransmitted as the ensemble level descriptor of the SMT, or as theservice level descriptor. FIG. 45 illustrates an example of transmissionof the EAS message descriptor included in the ensemble level, and FIG.46 illustrates an example of transmission of the EAS message descriptorincluded in the service level.

In the case that the EAS message descriptor is transmitted through theensemble level descriptor as shown in FIG. 45, the content contained inthe EAS message descriptor is applied to all services (e.g., TV service#1 and TV service #2) of a corresponding ensemble (e.g., ensemble #1) inthe same manner. If the EAS message descriptor is contained in theensemble level and transmitted, the necessity of sending the EAS messagedescriptor for each of the services of the SMT is eliminated.Accordingly, the size of the SMT may be reduced. When the EAS messagedescriptor is transmitted as the ensemble level descriptor, the value ofEAS_NRT_included_flag field shown in FIG. 44 may be set to 0. In thiscase, NRT associated information (i.e., disaster-related additionalinformation) cannot be transmitted except the CAP message.

In the case that the EAS message descriptor is transmitted as theservice level descriptor as shown in FIG. 46, the same content of theEAS message descriptor is contained in each service of the SMT. This mayincrease the size of the SMT compared to the case of transmission of thedescriptor as the ensemble level descriptor, but can advantageouslyallow transmission of the NRT service-associated information to expressadditional information associated with the emergency alert message(i.e., disaster-related additional information) since all thedescriptors of the SMT used in NRT are in the service level.

When the EAS message descriptor is transmitted as the service leveldescriptor, the value of the EAS_NRT_included_flag field shown in FIG.44 may be set to one of 0 and 1. If the value of theEAS_NRT_included_flag field is 0, it indicates that there is nodisaster-related additional information which is transmitted in NRT. Ifthe value is 1, it indicates that there is disaster-related additionalinformation which is transmitted in NRT.

The broadcast receiver extracts the EAS message descriptor by parsingthe received SMT included in the ensemble, processes the CAP messagecontained in the EAS message descriptor, and then displays disasterinformation in the form of a text at the lower end 601 of the screen asshown in FIG. 47. Herein, the EAS message descriptor may be included inthe ensemble level of the SMT or in the service level. In addition,while the disaster information in the form of a text is illustrated asbeing displayed at the lower end of the screen, it may be displayed atanother portion of the screen, for example, one of the upper end, leftside and right side. In addition, the disaster information in the formof a text may be scrolled from one side to the other.

As described above, the disaster-related additional informationbroadcast according to embodiments of the present invention may betransmitted in NRT. Herein, the disaster-related additional informationincludes various types of information such as image, video, and text,which may be greatly useful for the user when disaster happens.

FIG. 48 illustrates displaying the received disaster information in theform of a text contained in the EAS message descriptor at the lower end601 of the screen and displaying the disaster-related additionalinformation received in NRT in the form of an image or text at otherportions 602 to 604 of the screen at the same time. The screen shown inFIG. 48 is simply an example. The screen size and the disposition of thedisaster-related additional information may vary depending on the typesand the number of pieces of the disaster-related additional information.

In one embodiment, the disaster-related additional information may beconfigured in one file and transmitted in NRT.

In mobile broadcast, the real time (RT) service literally refers to aservice provided in real time. That is, this service is a time-dependentservice. On the other hand, the NRT service refers to a service providedin non-real time compared to the RT service. That is, the non-real timeservice is not time-dependent. For example, a broadcasting station maytransmit an RT service and provide an NRT service using a remainingbandwidth or a dedicated bandwidth. That is, the RT service and the NRTservice are transmitted over the same channel or different channels.

In another example, the broadcast receiver according is capable ofreceiving a non-real time (NRT) service through media such asterrestrial broadcast, cable, and the Internet.

The NRT service is stored in the storage medium of the broadcastreceiver, and is then displayed on a display device at a predeterminedtime or according to a request from the user. The NRT service may bestored in the form of a file in the storage. In one embodiment, thestorage medium may be a built-in HDD mounted in the broadcast receiver.In another embodiment, the storage medium may be an external HDD or auniversal serial bus (USB) memory connected to the exterior of abroadcast receiving system.

In one embodiment, one NRT service includes at least one content item(or referred to as content or NRT content), and one content itemincludes at least one file. In this present invention, the ‘file’ hasthe same meaning as the term ‘object’. A content item is the smallestunit that can be independently reproduced. For example, assume that newsis provided in non-real time and that the new includes news on theeconomy, politics and life. In this case, the news may be viewed as theNRT service, and each of the news on the economy, politics, and life maybe viewed as a content item. each of the news on the economy, politics,and life is configured in at least one files.

Content items/packets configuring an NRT service at the transmitter sidesuch as a broadcasting station are packetized according to the filetransfer protocol, and then packetized according to the asynchronouslayered coding/layered coding transport (ALC/LCT) scheme. The packetizedALC/LCT data is then packetized according to the UDP, and the packetizedALC/LCT/UDP data is in turn packetized according to the IP scheme toform ALC/LCT/UDP/IP data. The packetized ALC/LCT/UDP/IP data will bereferred to as IP datagram for simplicity of the description of thepresent invention. The OMA BCAST service guide information may alsoundergo the same process as for the content item/files to configure anIP datagram.

The IP datagrams for the NRT service are contained in at least one RSframe belonging to an ensemble (or referred to as a subnet) when theyare transmitted. An IP datagram of the OMA BCAST service guide may alsobe transmitted in the RS frame. In addition, similar to the mobileservice, access information for accessing the NRT service is signaled tothe SMT. That is, the SMT provides RT service or NRT service and accessinformation of the components (or content items) contained in eachservice.

Accordingly, if the service contained in the mobile broadcast is the NRTservice, signaling information including the access information of theFLUTE session, which carries content items/files configuring the NRTservice, may be extracted from the SMT. In addition, detailedinformation on content items configuring the NRT service may beextracted from the OMA BCAST service guide (SG) information.

At this time, the SMT contains one NRT service descriptor and one ormore capabilities descriptor for each NRT service in the service level.

The NRT service descriptor indicates whether an NRT service exists,identifies the consumption model of the NRT service, and provides otheroptional information about the NRT service. That is, the NRT servicedescriptor describes information items indicating that the servicedescribed in the service level of the SMT is an NRT service.

The capabilities descriptor provides a list of capabilities used for theNRT service or a content item (e.g., download protocol, FEC algorithm,wrapper/archive formats, compression algorithm, and media type). Inaddition, a nonessential protocol may be listed. That is, thecapabilities descriptor describes the capabilities of the filesconfiguring the NRT service.

Meanwhile, for the broadcast receiver to process disaster-relatedadditional information received in NRT and provide the processedinformation to the user, information allowing identifying the filesreceived in NRT as disaster-related additional information is needed.

In one embodiment of the present invention, the information foridentifying a file as disaster-related additional information issignaled to at least one of the NRT service descriptor and thecapabilities descriptor transmitted to the service level of the SMT.

FIG. 49 illustrates the syntax structure of a capabilities descriptoraccording to one embodiment of the present invention.

In FIG. 49, the descriptor_tag field (8 bits) is a descriptoridentifier. An identifier (or a tag value) to identify whether adescriptor is the capabilities descriptor is allocated to this field.

The descriptor_length field (8 bits) indicates the remaining length ofthis descriptor from the descriptor_length field to the end of thedescriptor in unit of byte.

The capability_code_count field (8 bit) indicates the number of valuesof capability_code. The essential_indicator field and capability_codefield are repeated by a value of the capability_code_count field.

The essential_indicator field (1 bit) indicates whether supporting thecapability indicated by capability_code is essential for meaningfulexistence of the NRT service or content item.

The capability_code field (7 bits) indicates a specific capability. Ifthe value of the capability_code field is greater than 0x6F, aformat_identifier field indicating an format identifier exists.

The capability_string_count field (8 bits) indicates the number ofvalues of the capability_string. The essential_indicator field,capability_category_code field, capability_string_length field, andcapability_string( ) field are repeated by the value of thecapability_string_count field.

The essential_indicator field (1 bit) indicates whether supporting thecapability indicated by capability_string is essential for meaningfulexistence of the NRT service or content item.

The capability_category_code field (7 bits) indicates the capabilitycategory of a subsequent string value.

The capability_string_length field (8 bits) indicates the length of asubsequent capability_string( ) field.

The capability_string( ) field is a string (i.e., a character string)including the capability.

In one embodiment, the capability_string( ) field, which is capable ofclassifying files, is used to indicate that a file is related todisaster-related additional information.

That is, by allocating a new string value (e.g., x-application/eas) tothe value of the capability_string( ) field, the received files with the“x-application/eas” capability is identified as containingdisaster-related additional information.

FIG. 50 illustrates the syntax structure of an NRT service descriptoraccording to one embodiment of the present invention.

In FIG. 50, the descriptor_tag field (8 bits) is a descriptoridentifier. An identifier (or a tag value) to identify whether adescriptor is the NRT service descriptor is allocated to this field.

The descriptor_length field (8 bits) indicates the remaining length ofthis descriptor from the descriptor_length field to the end of thedescriptor in unit of byte.

The consumption_model field (6 bits) signals an intended consumptionmodel for an NRT service associated with the descriptor.

The auto-update field (1 bit) indicates whether to provide an option forautomatic updating of the NRT service to the user.

The storage_reservation_present field (1 bit) indicates existence of thestorage_reservation field.

The default_content_size_present field (1 bit) indicates existence ofthe default_content_size field.

The storage_reservation field (24 bit) indicates the minimum storagecapacity of the receiver required to store a content item transmittedthrough the NRT service.

The default_content_size field (40 bit) indicates a default size for thecontent item.

In one embodiment of the present invention, the consumption model fieldindicating a description of a scheme in which an NRT service is providedis used to indicate that the NRT service is related to thedisaster-related additional information.

That is, a currently reserved value is allocated to the consumptionmodel field, and the files including a NRT service having this value areidentified as containing the disaster-related additional information.

FIG. 51 illustrates meanings of the values allocated to the consumptionmodel field. FIG. 51 illustrates an example of allocating 0x04 to theconsumption model field in the case that the NRT service is related tothe disaster-related additional information.

As described above, by signaling, to NRT service descriptor and/orcapabilities descriptor among the descriptors transmitted in the servicelevel of the SMT, the information for identifying whether the filesincluded in the NRT service contains disaster-related additionalinformation broadcast, the disaster-related additional information maybe efficiently provided using NRT.

According to one embodiment, the transmitter side may describe theinformation delivering the ESG corresponding to the NRT service in theGAT, and the broadcast receiver may combine this information and the SMTand download the ESG. The GAT includes information about a providersending the ESG. At this time, separately sending the ESG informationassociated with the EAS is more effective for quick transmission of thedisaster information. In this case, to distinguish the ESG from an ESGfor the existing SG data, the provider name may be allowed to representthe EAS.

FIG. 52 is a flowchart illustrating a method of the broadcast receiverreceiving and displaying an emergency alert message containing disasterinformation and disaster-related additional information according to oneembodiment of the present invention.

In FIG. 52, the emergency alert message containing disaster informationmay be carried in the EAS message descriptor of FIG. 43 or 44 andreceived, and the disaster-related additional information may bereceived in the form of a file in NRT. The information identifyingwhether the file is the disaster-related additional information may bereceived by being signaled to the capabilities descriptor of FIG. 49 orthe NRT service descriptor of FIG. 50. Herein, the EAS messagedescriptor may be one of the ensemble level descriptor and service leveldescriptor of the SMT, and each of the capabilities descriptor and NRTservice descriptor is one of the service level descriptors of the SMT.

That is, the mobile broadcast is tuned by a tuner of the broadcastreceiver (S651), and then a service signaling channel included in thetuned mobile broadcast is acquired (S652). Herein, the service signalingchannel may be encapsulated in the IP datagrams having a well-known IPdestination address and a well-known destination UDP port number. Inother words, all the IP datagrams (i.e., UDP/IP packets) transmittedthrough the service signaling channel have the same well-known target IPaddress and the same well-known target UDP port number. For example,when the SMT, RRT, and GAT are assumed to be transmitted through theservice signaling channel, all UDP/IP packets transmitting the SMT, RRT,and GAT have the same target IP address and the same target UDP portnumber. In addition, the target IP address and target UDP port numberare well-known values, namely, values known to the receiving systemaccording to agreement by the transmitting/receiving system.Accordingly, signaling tables contained in the service signaling channelmay be distinguished from each other by a table identifier. The tableidentifier may be table_id present in a signaling table or the heater ofa signaling table session. If necessary, table_id_extension may befurther referenced to distinguish the tables from each other.

Information of the signaling tables distinguished by the tablel_id fieldand/or table_id_extension field is stored in the storage unit of thebroadcast receiver (S653). In addition, whether the EAS messagedescriptor exists in the SMT is confirmed (S654). If the EAS messagedescriptor exists, the emergency alert message received through the EASmessage descriptor is processed and disaster information is displayed inthe form of a text on a portion of the screen, as shown in FIG. 47(S655).

In addition, whether the capabilities descriptor or NRT servicedescriptor exists in the SMT and whether an indication indicating that afile included in the NRT service is the EAS, i.e., disaster-relatedadditional information is signaled to at least one of the capabilitiesdescriptor and the NRT service descriptor are confirmed (S656).

When it is confirmed in step S656 that an indication indicating thedisaster-related additional information is signaled, the NRT service isdownloaded (S657). Then, whether the expiration time of the filescontained in the downloaded NRT service has passed (S658). If it isconfirmed that the expiration time has not passed, disaster-relatedadditional information included in at least one file received in NRT isdisplayed on a portion of the screen, as shown in FIG. 48 (S659).Herein, the disaster-related additional information may be various typesof information such as image, video, and text which are related to thedisaster information contained in the emergency alert message.

FIG. 53 is a flowchart illustrating a method of the broadcast receiverreceiving and displaying an emergency alert message containing disasterinformation and disaster-related additional information according toanother embodiment of the present invention.

In FIG. 53, the emergency alert message containing disaster informationmay be carried in the EAS message descriptor of FIG. 44, which includethe essential_content_linkage field, and received, and thedisaster-related additional information may be received in the form of afile in NRT. The information identifying whether the file is thedisaster-related additional information may be received by beingsignaled to the capabilities descriptor of FIG. 49 or the NRT servicedescriptor of FIG. 50. Herein, the EAS message descriptor may be one ofthe ensemble level descriptor and service level descriptor of the SMT,and each of the capabilities descriptor and NRT service descriptor isone of the service level descriptors of the SMT.

That is, the mobile broadcast is tuned by a tuner of the broadcastreceiver (S661), and then a service signaling channel included in thetuned mobile broadcast is acquired (S662). The details of the servicesignaling channel are identical to those illustrated with reference toFIG. 52, and thus a description thereof will be omitted.

Information of the signaling tables identified by the tablel_id and/ortable_id_extension field included in each signaling table of the servicesignaling channel is stored in the storage unit of the broadcastreceiver (S663). In addition, whether the EAS message descriptor existsin the SMT is confirmed (S664). If the EAS message descriptor exists,the emergency alert message received through the EAS message descriptoris processed and disaster information is displayed in the form of a texton a portion of the screen, as shown in FIG. 47 (S665).

In addition, whether an NRT service related to the EAS exists isconformed (S666). Herein, whether an NRT service related to the EASexists may be conformed using the num_associated_service field of theEAS message descriptor. If one or more NRT service related to the EASexists, the EAS message descriptor provides an identifier of the NRTservice related to the EAS (associated_service_id).

In step S666, when existence of one or more NRT service related to theEAS is confirmed, an NRT service is downloaded using the correspondingNRT service identifier (S667). Then, whether the value of theessential_content_linkage field of the EAS message descriptor is 0 isconfirmed (S668). The essential_content_linkage field indicates thevalue of linkage between a file included in the NRT service and acontent item in the ESG. If the value of the essential_content_linkagefield is 0, the user interface (UI) displays a list of NRT services forthe EAS (S669). If the value is not 0, the UE displays a file having thevalue of the essential_content_linkage field as the value ofcontent_linkage on the screen (S670).

As described above, an emergency alert message containing actualdisaster information (or content) may be transmitted in the form of aCAP message or syntax.

At this time, an emergency alert message in the form of the CAP or anemergency alert message in the form of syntax may be encapsulated in anIP datagram and transmitted.

That is, as shown in FIG. 54, the IP datagram may be in the form of anIP packet configured with a header and a payload, and the header may beconfigured with an IP header and a UDP header. In addition, the payloadincludes an emergency alert message in the form of the CAP or anemergency alert message in the form of syntax. The emergency alertmessage in the form of syntax included in the payload has the form of atable. This table will be referred to as an EAS table. When theemergency alert message in the form of the CAP is transmitted by thepayload, the length of the payload may be calculated based on the lengthof the IP/UDP header.

FIG. 55 is a view illustrating the syntax structure of an emergencyalert system descriptor (emergency_alerting_system_descriptor ( ))transmittable by the payload of FIG. 54. The descriptor may be asession, and the EAS table may be configured using at least onedescriptor.

In FIG. 55, the descriptor_tag field (8 bits) is a descriptoridentifier. An identifier (or a tag value) to identify whether adescriptor is the emergency alert system descriptor is allocated.

The descriptor_length field (8 bits) indicates the remaining length ofthis descriptor from the descriptor_length field to the end of thedescriptor in unit of byte.

The descriptor_number field (4 bits) indicates the number of the currentdescriptor among the descriptors included in the EAS table.

The last_descriptor_number field (4 bits) indicates the number of thelast descriptor among the descriptors included in the EAS table.

The EAS_event_id field (16 bits) indicates an identifier of an EASevent.

The EAS_originator_code field (24 bits) indicates an entity havingactivated the EAS.

The EAS_event_code_length field (8 bits) indicates the length of theEAS_event_code field.

The EAS_event_code field (variable) indicates an EAS event, i.e., a typeof the EAS. For example, a type of the emergency alert such as flood,earthquake and terrorism may be indicated along with the importance of aspecific emergency such as large earthquake, medium earthquake, andsmall earthquake.

The alert_message_time_remaining field (8 bits) indicates the remainingoutput time, of an emergency alert message.

The event_start_time field (32 bits) indicates the start time of displayof the EAS event.

The event_duration field (16 bits) indicates the duration time ofdisplay of the EAS event.

The alert_priority field (4 bits) indicates the priority or importanceof the EAS event. That is, depending on the value of the alert_priorityfield, processing of the received emergency alert message is determined.In other words, whether to unconditionally ignore the emergency alertmessage or ignore the same under certain conditions, or to compulsorilytune the message to a specific broadcast channel is determined.

The EAS_major_channel_number field (8 bits) indicates a major channelnumber related to the broadcast channel.

The EAS_minor_channel_number field (8 bits) indicates a minor channelnumber related to the broadcast channel.

The alert_text_length field (16 bits) indicates the total number ofbytes of the alert_text( ) field.

The alert_text( ) field (variable) includes disaster information to bedisplayed in the form of a text.

The location_code_count field (8 bits) counts region definitionsfollowing the ‘for loop’ syntax.

The state_code field (8 bits) indicates a state or territory associatedwith an emergency alert. The field may have value between 0 and 99.

The county subdivision field (4 bits) may have a value between 0 and 9which defines the county division (state subdivision).

The county_code field (10 bits) expresses a specific county associatedwith the emergency alert among other states. The field may have a valuebetween 0 and 999.

According to one embodiment of the present invention, the emergencyalert message may be transmitted at the service level or componentlevel. In the case that the emergency alert message is transmitted atthe service level, the emergency alert message is considered as oneservice, which will be referred to as the EAS service for ease ofdescription. In addition, for the broadcast receiver to support the EASservice, signaling of information to identify the EAS service(hereinafter, referred to as EAS service identifying information) isneeded.

In one embodiment of the present invention, one of the reserved valuesof the MH_service_category field in the service loop of the SMT is usedfor the EAS service identifying information. According to oneembodiment, if a service in the service loop of the SMT is an EASservice, 0x04 may be allocated as the value of the MH_service_categoryfield, as shown in FIG. 56. In this case, the broadcast receiver mayrecognize that signaling information of the service described in theservice loop of the SMT is the signaling information of the EAS service.Herein, 0x04 allocated as the value of the MH_service_category field issimply an example, any category value between 0x00 and 0xFF which is notused by existing services may be allocated. To identify the EAS service,the MH_service_id field may be further used.

In the case that the emergency alert message is transmitted by aseparate service, transmitting signaling once for each ensemble issufficient, and therefore this case is advantageous in view of use of abandwidth.

Meanwhile, in the case that the emergency alert message is transmittedat the component level, the emergency alert message is considered as onecomponent just as a audio component and a video component. Thiscomponent will be referred to as an EAS component for ease ofdescription. For the broadcast receiver to support the EAS component,signaling of information to identify an EAS component (hereinafter,referred to as EAS component identifying information) is needed.

In one embodiment of the present invention, one of the reserved valuesof the component_type field in component_descriptor( ) shown in FIG. 38,among the component level descriptors of the SMT is used for the EAScomponent identifying information. For example, if a component in thecomponent loop of the SMT is the EAS component, 43 is allocated as thevalue of the component_type field. In this case, the broadcast receivermay recognize that the signaling information of the component describedin the component loop of the SMT is the signaling information of the EAScomponent. Herein, allocation of 43 to the component_type field issimply an example. Any value between 43 and 71 that is not used by theexisting components may be allocated.

The component_type field in component_descriptor( ) indicates a valuefor identifying the encoding format of a component. This identificationvalue may be one of the values allocated for payload_type of the RTP/AVPstream, one of the values predetermined according to agreement by thetransmitter/receiver side, or a dynamic value between 96 and 127. Forthe components configuring media transmitted via the RTP, a value of thecomponent_type field needs to be identical to the value of payload_typein the RTP header of an IP stream which transmits a correspondingcomponent.

In addition, the component_data (component_type) field, which variesdepending upon the value of the component_type field, provides encodingparameters and/or other parameters which are necessary for rendering ofa corresponding component. That is, the structure of an component_dataelement is determined by the value of the component_type field.

For example, if the value of the component_type field is 35, thecomponent_data( ) field provides component data for an H.264/AVC videostream.

If the component_type field is 38, the component_data( ) field providesdata for FLUTE file delivery.

If the component_type field is 43, the component_data( ) field providessignaling information for an emergency alert message, as shown in FIG.57.

FIG. 57 illustrates an example of the bit stream syntax structure ofcomponent_data( ) which provides signaling information for an emergencyalert message. Fields of the component_data( ) are described below.

In FIG. 57, the EAS_event_ID field (16 bits) indicates a uniqueidentifier of an EAS event corresponding to the emergency alert message.

The payload_type field (2 bits) indicates whether an emergency alertmessage transmitted in the form of an IP datagram is of the CAP type orthe syntax type. In this case, the broadcast receiver is allowed toidentify, using the payload_type field, whether the received emergencyalert message is CAP type data or syntax type data. That is, thebroadcast receiver is allowed to identify the data type of the emergencyalert message at the component level.

In another embodiment of the present invention, by allocating thepayload_type field to the reserved bits in the component level of theSMT, the data type of the emergency alert message may be identified atthe component level.

In another embodiment of the present invention, by allocating thepayload_type field to the reserved bits in the service level of the SMT,the data type of the emergency alert message may be identified at theservice level.

The status field (6 bits) indicates the status of an emergency alertmessage.

The urgency field (8 bits) indicates the degree of urgency of a disastercontained in the emergency alert message.

The severity field (8 bits) indicates the degree of severity of adisaster contained in the emergency alert message.

The certainty field (8 bits) indicates the degree of certainty of adisaster contained in the emergency alert message.

The event_start_time field (32 bits) indicates the start time of displayof a disaster alert contained in the emergency alert message.

The event_duration field (16 bits) indicates the duration time of adisaster alert contained in the emergency alert message.

Meanwhile, in one embodiment, a new table is defined to signal signalinginformation for an emergency alert message. This table will be referredto as an emergency alert table (EAT) in this embodiment.

An IP datagram including the EAT may be transmitted through a servicesignaling channel.

In the case that the EAT is transmitted through the service signalingchannel, the EAS_ensemble_indicator field included in the FIC chunkpayload of FIG. 42 may indicate whether the EAT is transmitted throughthe service signaling channel of a corresponding ensemble. For example,if the value of the EAS_ensemble_indicator field is 1, it may indicatethat the EAT is transmitted through the service signaling channelincluded in the ensemble. If the value is 0, it may indicate that theEAT is not transmitted.

The EAT may provide access information of an emergency alert messagetransmitted in the form of an IP datagram. The access information mayinclude an IP address and a UDP port number.

The service signaling channel through which the EAT is transmitted mayfurther include a signaling table (i.e., at least one of the SMT, GAT,RRT, SLT, and CIT) as well as the EAT. At this time, IP datagrams of theservice signaling channel may have the same well-known IP address andwell-known UDP port number. Accordingly, the EAT included in the servicesignaling channel is identified by the table identifier. That is, thetable identifier may be table_id existing in the header of thecorresponding table or corresponding table section. If necessary,table_id_extension may be further referenced.

FIG. 58 illustrates the bit stream syntax structure of an EAT sectionaccording to one embodiment of the present invention. While the EATsection is illustrated as being drafted in the form of an MPEG-2 privatesection, the format of the data in the EAT section may have any form. Atthis time, whether the EAT is configured with one section or a pluralityof sections may be confirmed through the table_id field, section_numberfield, and last_section_number field in the EAT section. In addition, acorresponding table may be completed by removing IP headers and UDPheaders of the IP datagrams from the service signaling channel andcollecting sections having the same table identifier. For example, whenthe sections having the table identifier allocated to the EAT, one EATmay be completed.

Hereinafter, the fields transmittable through the EAT section will bedescribed.

The table_id field (8 bits) is a field to identify the type of thetable. Through this field, it may be confirmed that the table is theEAT.

The section_syntax_indicator field (1 bit) is an indicator to define thesection form of the EAT. The section format may be, for example,short-form syntax (‘0’) of MPEG.

The private_indicator field (1 bit) indicates whether the EAT followsthe private section.

The section_length field (12 bits) indicates the section length of theremaining EAT subsequent to a corresponding field.

The table_id_extension field (16 bits) is table-dependent, and is alogical portion of the table_id field which provides the range of theremaining fields. The table_id_extension field includes aEAT_protocol_version field and a ensemble_id field.

The EAT_protocol_version field (8 bits) indicates a protocol version toallow the EAT that parameters having a different structure over thosedefined in a current protocol transmit.

The ensemble_id field (8 bits) is an ID value related to thecorresponding ensemble, and a value between 0x00 and 0x3F may beallocated thereto. Preferably, the value of this field is drawn from theparade_id of TPC data. In the case that the ensemble is transmittedthrough a primary RS frame, the most significant bit (MSB) is set to‘0’, and the remaining 7 bits are used as a value of parade_id of acorresponding parade. In the case that the ensemble is transmittedthrough a secondary RS frame, the MSB is set to ‘1’, and the remaining 7bits are used as a value of parade_id of a corresponding parade.

The version_number field (5 bits) indicates the version number of theEAT.

The current_next_indicator field (1 bit) indicates whether the EATsection is currently applicable.

The section_number field (8 bits) indicates the number of a current EATsection.

The last_section_number field (8 bits) indicates the number of the lastsection configuring the EAT.

The num_MH_services field (8 bits) indicates the number of mobileservices in an EAT section.

By performing ‘for’ loop (or referred to as mobile service loop) by thenumber of mobile services corresponding to the value of thenum_MH_services field, signaling information about a plurality of mobileservices is provided. That is, signaling information about each of themobile services is indicated for each of the mobile services included inthe EAT section. At this time, field information may be provided foreach mobile service as follows.

The MH_service_id field (16 bits) indicates a value that uniquelyidentifies a mobile service.

The MH_service_status field (2 bits) identifies the status of the mobileservice. Herein, the MSB indicates whether the mobile service is active(‘1’) or non-active (‘0’), and the LSB indicates whether the mobileservice is hidden (‘1’) or not (‘0’).

The SP_indicator field (1 bit) indicates whether service protection ofthe mobile service is applied. If the value of the SP_indicator field is1, the service protection is applied at least one of the componentsrequired for the mobile service to provide meaningful presentationmobile service.

The urgency field (8 bits) indicates the degree of urgency of anemergency alert message contained in the mobile service.

The severity field (8 bits) indicates the degree of severity of theemergency alert message contained in the mobile service.

The certainty field (8 bits) indicates the degree of certainty of theemergency alert message contained in the mobile service.

The event_start_time field (32 bits) indicates the start time of displayof the emergency alert message contained in the mobile service.

The event_duration field (16 bits) indicates the duration time ofdisplay of the emergency alert message contained in the mobile service.

In the case that the IP_version_flag field (1 bit) is set to ‘1’, itindicates that the service_source_IP_address field andservice_destination_IP_address field are IPv6 addresses. In the casethat the IP_version_flag field (1 bit) is set to ‘0’, it indicates thatthe service_source_IP_address field and service_destination_IP_addressfield are IPv4 addresses.

In the case that the service_source_IP_address_flag field (1 bit) is setto ‘1’, it indicates that a value of the source IP address for theservice exists.

In the case that the service_destination_IP_address_flag field (1 bit)is set to ‘1’, it indicates that a value of the destination IP addressfor the service exists.

The IP_payload_type field (2 bit) indicates whether the emergency alertmessage transmitted in the form of an IP datagram is of the CAP type orthe syntax type.

The service_source_IP_address field (32 or 128 bits) needs to beinterpreted when the service_source_IP_address_flag field is set to ‘1’,but does not need to be interpreted when theservice_source_IP_address_flag field is set to ‘0’. In the case that theservice_source_IP_address_flag field is set to ‘1’, and theIP_version_flag field is set to ‘0’, the above field indicates a 32 bitIPv4 address representing the source of the mobile service. In the casethat the IP_version_flag field is set to ‘1’, the above field indicatesa 32 bit IPv6 address the source of the mobile service.

The service_destination_IP_address field (32 or 128 bits) needs to beinterpreted when the service_destination_IP_address_flag field is set to‘1’, but does not need to be interpreted when theservice_destination_IP_address_flag field is set to ‘0’. In the casethat the service_destination_IP_address_flag field is set to ‘1’, andthe IP_version_flag field is set to ‘0’, the above field indicates a 32bit destination IPv4 address for the mobile service. In the case thatthe service_destination_IP_address_flag field is set to ‘1’, and theIP_version_flag field is set to ‘1’, the above field indicates a 64 bitdestination IPv6 address for the mobile service.

Meanwhile, if the value of the severity field is 1, i.e., if a disasteris very severe, compulsory tuning information is signaled.

That is, the force_channel_num field (8 bits) indicates the channelnumber to be compulsorily tuned, and the force_service_id field (16bits) indicates a service identifier to be compulsorily tuned.

The num_MH_EAS_descriptor field (8 bits) indicates the number ofdescriptors that provide additional information of the service level.

A number of MH_EAS_descriptor( ) fields corresponding to the value ofthe num_MH_EAS_descriptor field are included in the service loop toprovide additional information about the emergency alert message.

If the emergency alert message is not transmitted in the form of an IPdatagram, the emergency alert message may be included in theMH_EAS_descriptor( ) and transmitted. To this end, the EAT may furtherinclude information for identifying whether the emergency alert messageis transmitted in the form of an IP datagram or included in the EAT andtransmitted.

FIG. 59 is a flowchart illustrating a method of the broadcast receiverreceiving and displaying an emergency alert message containing disasterinformation according to one embodiment of the present invention.

In FIG. 59, the emergency alert message containing disaster informationmay received in the form of an IP datagram, and the signalinginformation including the access information of the emergency alertmessage may be signaled to the EAT and received.

That is, the mobile broadcast is tuned by a tuner of the broadcastreceiver (S701), and then an IP datagram of a service signaling channeland an IP datagram including the emergency alert message are identifiedthrough IP filtering (S702). In one embodiment, the IP address and theUDP port number for accessing the IP datagram of the service signalingchannel may be a well-known IP destination address and a well-knowndestination UDP port number, respectively. In addition, the IP addressand the UDP port number for accessing the IP datagram of the emergencyalert message may be signaled to the EAT. In another embodiment, the IPaddress and the UDP port number for accessing the IP datagram of theemergency alert message may be signaled to the SMT.

Information of each signaling table of the service signaling channelidentified by the tablel_id field and/or table_id_extension fields ofthe signaling table is stored in the storage unit of the broadcastreceiver (S703). In addition, whether the EAT exists in the servicesignaling channel is confirmed (S704). The confirmation may be performedusing the tablel_id field and/or table_id_extension field of the EAT. Ifthe EAT exists, the emergency alert message in the form of the IPdatagram is processed using the information included in the EAT. Thatis, using the value of the payload_type field of the EAT, whether thedata received with a payload of the IP datagram is a CAP type emergencyalert message of a syntax type emergency alert message is confirmed(S705). If the data is a CAP type emergency alert message, a CAP parser(not shown) processes the emergency alert message (S706). If the data isa syntax type emergency alert message, a syntax parser (not shown)processes the emergency alert message (S707). Then, the processedmessage is displayed in the form of a text on a portion of the screen asshown in FIG. 47 (S708).

In addition, whether the capabilities descriptor or NRT servicedescriptor exists in the SMT and whether an indication indicating that afile included in the NRT service is the EAS, i.e., disaster-relatedadditional information is signaled to at least one of the capabilitiesdescriptor and the NRT service descriptor are confirmed (S656).

Herein, at least one file including the additional information relatedto the emergency alert message (i.e., disaster-related additionalinformation) may be received in NRT, and the signaling information forthe disaster-related additional information may be signaled in theservice level or component level of the SMT. Then, the received file isprocessed in NRT based on the signaling information of thedisaster-related additional information of the SMT, and thedisaster-related additional information received through the file isdisplayed on a portion of the screen. The disaster-related additionalinformation may be various types of information such as image, video,and text which are related to the disaster information contained in theemergency alert message.

FIG. 60 illustrates a block diagram of a receiving system (i.e.,broadcast receiver) to receive and process services such as a mobileservice, an EAS service, and an NRT service and so on transmittedthrough mobile broadcast according to an embodiment of the presentinvention. Referring to FIG. 60, the arrow shown in dotted lineindicates a data path, and the arrow shown in slid line indicates acontrol signal path.

The receiving system of FIG. 60 may include a controller 2100, a tuner2111, a demodulator 2112, an equalizer 2113, a known sequence detector(or known data detector) 2114, a block decoder 2115, a primaryReed-Solomon (RS) frame decoder 2116, a secondary RS frame decoder 2117,a signaling decoder 2118, and a baseband operation controller 2119. Thereceiving system according to the present invention may further includean FIC handler 2121, a service manager 2122, a service signaling handler2123, and a first storage unit 2124. The receiving system according tothe present invention may further include a primary RS frame buffer2131, a secondary RS frame buffer 2132, and a transport packet (TS)handler 2133. The receiving system according to the present inventionmay further include an Internet Protocol (IP) datagram handler 2141, adescrambler 2142, an User Datagram Protocol (UDP) datagram handler 2143,a Real-time Transport Protocol/Real-time Transport Control Protocol(RTP/RTCP) datagram handler 2144, a Network Time Protocol (NTP) datagramhandler 2145, a service protection stream handler 2146, a second storageunit 2147, an Asynchronous Layered Coding/Layered Coding Transport(ALC/LCT) stream handler 2148, an Extensible Mark-up Language (XML)parser 2150, and a Field Device Tool (FDT) handler 2151. The receivingsystem according to the present invention may further include anAudio/Video (A/V) decoder 2161, a file decoder 2162, a third storageunit 2163, a middle ware (M/W) engine 2164, and a Service Guide (SG)handler 2165. The receiving system according to the present inventionmay further include an Electronic Program Guide (EPG) manager 2171, anapplication manager 2172, and an User Interface (UI) manager 2173.

Herein, for simplicity of the description of the present invention, thetuner 2111, the demodulator 2112, the equalizer 2113, the known sequencedetector (or known data detector) 2114, the block decoder 2115, theprimary RS frame decoder 2116, the secondary RS frame decoder 2117, thesignaling decoder 2118, and the baseband operation controller 2119 willbe collectively referred to as a baseband processor 2110. The FIChandler 2121, the service manager 2122, the service signaling handler2123, and the first storage unit 2124 will be collectively referred toas a service multiplexer 2120. The primary RS frame buffer 2131, thesecondary RS frame buffer 2132, and the TS handler 2133 will becollectively referred to as an IP adaptation module 2130. The IPdatagram handler 2141, the descrambler 2142, the UDP datagram handler2143, the RTP/RTCP datagram handler 2144, the NTP datagram handler 2145,the service protection stream handler 2146, the second storage unit2147, the ALC/LCT stream handler 2148, the XML parser 2150, and the FDThandler 2151 will be collectively referred to as a common IP module2140. The A/V decoder 2161, the file decoder 2162, the third storageunit 2163, the M/W engine 2164, and the SG handler 2165 will becollectively referred to as an application module 2160.

The terms used in FIG. 60 are general terms that are currently beingbroadly used. However, according to the advent of new technology, termsdeemed to be most appropriate by the applicant are also arbitrarily usedin the present invention. The definition of such terms will be describedclearly and in detail during the description of the correspondingportion of the present invention. Therefore, the terms used in thepresent invention should be understood by the significance lying withinthe terms and not merely by the term itself.

The baseband operation controller 2119 configured as shown in FIG. 60controls the operation of each block included in the baseband processor2110.

By tuning the receiving system to the frequency of a specific physicalchannel (or physical transmission channel (PTC)), the tuner 2111performs a role enabling the receiving system to receive main servicedata, which correspond to broadcast signals for fixed broadcastreceiving systems, and mobile service data, which correspond tobroadcast signals for mobile broadcast receiving systems. The mobileservice data may include an emergency alert message. The tuner 2111down-converts the frequency of the tuned specific channel to anintermediate frequency (IF) and outputs the IF to the demodulator 2112and the known sequence detector 2114. At this point, the tuner 2111 mayreceive main service data and mobile service data that are real-timedata and receive non-real time service data. Herein, the non-real timeservice data may include additional information (i.e., disasterrelated-additional information).

The demodulator 2112 performs self-gain control, carrier wave recovery,and timing recovery on the passband digital IF signal being inputtedfrom the tuner 2111, so as to create a baseband signal. Then, thedemodulator 2112 outputs the read baseband signal to the equalizer 2113and the know sequence detector 2114. When performing carrier waverecovery and timing recovery, the demodulator 2112 may use the knowndata symbol sequence received from the known sequence detector 2114), soas to enhance the demodulating performance.

The equalizer 2113 compensates the channel distortion included in thedemodulated signal, thereby outputting the processed signal to the blockdecoder 2115. The equalizer 2113 may enhance the equalizing performanceby using the known data symbol sequence received from the known sequencedetector 2114. Also, the equalizer 2113 may receive feedback on thedecoding result of the block decoder 2113, thereby enhancing theequalizing performance.

The known sequence detector 2114 detects the position of the known databeing inputted by the transmitting system from the input/output data ofthe demodulator 2112, i.e., data prior to being processed with thedemodulation process or data being partially processed with thedemodulation process. Then, along with the detected positioninformation, the known sequence detector 2114 outputs the known datasequence generated from the detected position to the demodulator 2112,the equalizer 2113, and the baseband operation controller 2119.Additionally, the known sequence detector 2114 provides to the blockdecoder 2115 with information enabling the block decoder 2115 todifferentiate mobile service data processed with additional encoding bythe transmitting system from main service data that are not processedwith any additional encoding.

If the data channel-equalized by the equalizer 2113 and inputted to theblock decoder 2115 correspond to data processed with both block-encodingof serial concatenated convolution code (SCCC) method andtrellis-encoding by the transmitting system (i.e., data within the RSframe, signaling data), the block decoder 2115 may performtrellis-decoding and block-decoding as inverse processes of thetransmitting system. On the other hand, if the data channel-equalized bythe equalizer 2113 and inputted to the block decoder 2115 correspond todata processed only with trellis-encoding and not block-encoding by thetransmitting system (i.e., main service data), the block decoder 2115may perform only trellis-decoding.

The signaling decoder 2118 performs decoding on signaling data inputtedafter being channel-equalized by the equalizer 2113. It is assumed thatthe signaling data (or signaling information) inputted to the signalingdecoder 2118 correspond to data processed with both block-encoding andtrellis-encoding by the transmitting system. According to an embodimentof the present invention, the signaling data includes TPC (TransmissionParameter Channel) data and FIC (Fast Information Channel). For example,the signaling decoder 2118 performs regressive turbo decoding using aparallel concatenated convolution code (PCCC) method on the data of thesignaling information region among the inputted data. Then, thesignaling decoder 2118 separates the FIC data and TPC data from theturbo-decoded signaling data. Also, the signaling decoder 2118 performsRS-decoding on the separated TPC data as an inverse process of thetransmitting system, thereby outputting the RS-decoded TPC data to thebaseband operation controller 2119. Furthermore, the signaling decoder2118 performs deinterleaving on the separated FIC data in subframe unitsand then performs RS-decoding on the deinterleaved FIC data as aninverse process of the transmitting system, thereby outputting theRS-decoded data to the FIC handler 2121. The transmission unit of theFIC data being deinterleaved and RS-decoded by the signaling decoder2118 and being outputted to the FIC handler 2121 corresponds to FICsegments.

The FIC handler 2121 receives FIC data from the signaling decoder 2118,so as to extract signaling information for service acquisition (i.e.,mapping information between an ensemble and a mobile service). In orderto do so, the FIC handler 2121 may include an FIC segment buffer, an FICsegment parser, and an FIC chunk parser.

The FIC segment buffer buffers FIC segment groups being inputted in M/Hframe units from the signaling decoder 2118, thereby outputting thebuffered FIC segments to the FIC segment parser. Thereafter, the FICsegment parser extracts the header of each FIC segment stored in the FICsegment buffer so as to analyze the extracted headers. Then, based uponthe analyzed result, the FIC segment parser outputs the payload of therespective FIC segments to the FIC chunk parser. The FIC chunk parseruses the analyzed result outputted from the FIC segment parser so as torecover the FIC chunk data structure from the FIC segment payloads,thereby analyzing the received FIC chunk data structure. Subsequently,the FIC chunk parser extracts the signaling information for serviceacquisition. The signaling information acquired from the FIC chunkparser is outputted to the service manager 2122. According to anembodiment of the present invention, the FIC segment header includes awake_up_indicator field. Reference may be made to FIG. 39 or FIG. 40 forthe detailed description of the wake_up_indicator field. Furthermore,according to an embodiment of the present invention, the FIC chunkpayload includes an EAS_ensemble_indicator field. Reference may be madeto FIG. 42 for the detailed description of the EAS_ensemble_indicatorfield.

Meanwhile, the service signaling handler 2123 is configured of a servicesignaling buffer and a service signaling parser, and the servicesignaling handler 2123 buffers table sections, for example, SMT sectionsand EAT sections of a service signaling channel being transmitted fromthe UDP datagram handler 2143, thereby analyzing and processing thebuffered table sections. The SMT information and the EAT informationprocessed by the service signaling handler 2123 is also outputted to theservice manager 2122.

According to an embodiment of the present invention, the servicesignaling channel transmitting the SMT section and/or the EAT section isincluded in a corresponding RS frame in a UDP/IP packet form havingwell-known destination IP address and well-known destination UDP portnumber and is received. Accordingly, the receiving system may parse theSMT section and descriptors of the SMT section without requiring extrainformation. This is identically applied to the EAT.

Furthermore, the SMT section provides signaling information (includingIP access information) about all services within the ensemble that theSMT section is included. Therefore, the receiving system may access anIP stream component belonging to a desired service by using informationparsed from the SMT section, thereby providing the service to the user.In addition, the receiving system may access the emergency alert messageby using EAS-related signaling information included in the EAT, therebyproviding the disaster information to the user.

If the service is an NRT service, access information of an FLUTE sessionthat transmits content/files configuring of the NRT service may beextracted from the SMT.

The information parsed from the SMT is collected by the service manager2122 and is stored in the first storage unit 2124. The service manager2122 stores the information extracted from the SMT as a service map anda guide data form in the first storage unit 2124.

That is, service manager 2122 uses the signaling information collected(or gathered) from the FIC handler 2121 and the service signalinghandler 2123 so as to configure a service map, and the service manager2122 uses the service guide (SG) collected from the service guide (SG)handler 2165 so as to configure a program guide. Then, the servicemanager 2122 refers to the configured service map and program guide tocontrol the baseband operation controller 2119 so that the user canreceive the mobile service he (or she) wishes. Also, depending upon theuser's input, the service manager 2122 may perform controllingoperations enabling the program guide to be displayed on at least oneportion of the display screen.

The first storage unit 2124 stores the service map and service guidedrawn up by the service manager 2122. Also, based upon the requests fromthe service manager 2122 and the EPG manager 2171, the required data areextracted from the first storage unit 2124, which are then transferredto the service manager 2122 and/or the EPG manager 2171.

The baseband operation controller 2119 receives the known data placeinformation and TPC data, thereby transferring M/H frame timeinformation, information indicating whether or not a data group existsin a selected parade, place information of known data within acorresponding data group, power control information, and so on to eachblock within the baseband processor 2110.

Meanwhile, according to the present invention, the transmitting systemuses RS frames by encoding units. Herein, the RS frame may be dividedinto a primary RS frame and a secondary RS frame. However, according tothe embodiment of the present invention, the primary RS frame and thesecondary RS frame will be divided based upon the level of importance ofthe corresponding data.

The primary RS frame decoder 2116 receives the data outputted from theblock decoder 2115. At this point, according to the embodiment of thepresent invention, the primary RS frame decoder 2116 receives the mobileservice data or NRT service data that have been Reed-Solomon(RS)-encoded and/or cyclic redundancy check (CRC)-encoded from the blockdecoder 2115. The primary RS frame decoder 2116 receives the SMT sectiondata or the OMA BCAST SG data that have been Reed-Solomon (RS)-encodedand/or cyclic redundancy check (CRC)-encoded from the block decoder2115.

In other words, the primary RS frame decoder 2116 receives at least oneof the mobile service data, the NRT service data, the SMT section dataand the OMA BCAST SG data but no main service data. The primary RS framedecoder 2116 performs inverse processes of the RS frame encoder (notshown) included in the digital broadcast transmitting system, therebycorrecting errors existing within the primary RS frame. Morespecifically, the primary RS frame decoder 2116 forms a primary RS frameby grouping a plurality of data groups and, then, correct errors inprimary RS frame units. In other words, the primary RS frame decoder2116 decodes primary RS frames, which are being transmitted for actualbroadcast services. The primary RS frame decoded by the primary RS framedecoder 2116 is output to the primary RS frame buffer 2131. The primaryRS frame buffer 2131 buffers the primary RS frame, and then configuresan M/H TP in each row unit. The M/H TPs of the primary RS frame outputsto the TP handler 2133.

Additionally, the secondary RS frame decoder 2117 receives the dataoutputted from the block decoder 2115. At this point, according to theembodiment of the present invention, the secondary RS frame decoder 2117receives the mobile service data or the NRT service data that have beenRS-encoded and/or CRC-encoded from the block decoder 2115. The secondaryRS frame decoder 2117 receives the SMT section data or the OMA BCAST SGdata that have been Reed-Solomon (RS)-encoded and/or cyclic redundancycheck (CRC)-encoded from the block decoder 2115.

That is, the secondary RS frame decoder 2117 receives at least one ofthe mobile service data, the NRT service data, the SMT section data andthe OMA BCAST SG data but no main service data. The secondary RS framedecoder 2117 performs inverse processes of the RS frame encoder (notshown) included in the digital broadcast transmitting system, therebycorrecting errors existing within the secondary RS frame. Morespecifically, the secondary RS frame decoder 2117 forms a secondary RSframe by grouping a plurality of data groups and, then, correct errorsin secondary RS frame units. In other words, the secondary RS framedecoder 2117 decodes secondary RS frames, which are being transmittedfor mobile audio service data, mobile video service data, guide data,and so on. The secondary RS frame decoded by the secondary RS framedecoder 2117 is output to the secondary RS frame buffer 2132. Thesecondary RS frame buffer 2132 buffers the secondary RS frame, and thenconfigures an M/H TP in each row unit. The M/H TPs of the secondary RSframe outputs to the TP handler 2133.

The TP handler 2133 consists of a TP buffer and a TP parser. The TPhandler 2133 buffers the M/H TPs inputted from the primary RS framebuffer 2131 and the secondary RS frame buffer 2132, and then extractsand analyzes each header of the buffered M/H TPs, thereby recovering IPdatagram from each payload of the corresponding M/H TPs. The recoveredIP datagram is outputted to the IP datagram handler 2141.

The IP datagram handler 2141 consists of an IP datagram buffer and an IPdatagram parser. The IP datagram handler 2141 buffers the IP datagramdelivered from the TP handler 2133, and then extracts and analyzes aheader of the buffered IP datagram, thereby recovering UDP datagram froma payload of the corresponding IP datagram. The recovered UDP datagramis outputted to the UDP datagram handler 2143.

If the UDP datagram is scrambled, the scrambled UDP datagram isdescrambled by the descrambler 2142, and the descrambled UDP datagram isoutputted to the UDP datagram handler 2143. For example, when the UDPdatagram among the received IP datagram is scrambled, the descrambler2142 descrambles the UDP datagram by inputting an encryption key and soon from the service protection stream handler 2146, and outputs thedescrambled UDP datagram to the UDP datagram handler 2143.

The UDP datagram handler 2143 consists of an UDP datagram buffer and anUDP datagram parser. The UDP datagram handler 2143 buffers the UDPdatagram delivered from the IP datagram handler 2141 or the descrambler2142, and then extracts and analyzes a header of the buffered UDPdatagram, thereby recovering data transmitted through a payload of thecorresponding UDP datagram. If the recovered data is an RTP/RTCPdatagram, the recovered data is outputted to the RTP/RTCP datagramhandler 2144. If the recovered data is also an NTP datagram, therecovered data is outputted to the NTP handler 2145. Furthermore, if therecovered data is a service protection stream, the recovered data isoutputted to the service protection stream handler 2146. And, if therecovered data is an ALC/LCT stream, the recovered data is outputted tothe ALC/LCT steam handler 2148. Furthermore, if the recovered data arethe SMT section data or the EAT section data, the recovered data areoutputted to the service signaling section handler 2123.

At this point, since the service signaling channel transmitting the SMTsection or the EAT section is an IP datagram having well-knowndestination IP address and well-known destination UDP port number, theIP datagram handler 2141 and the UDP datagram handler 2143 may outputthe data included in the SMT section and/or the EAT section withoutrequiring extra information to the service signaling section handler2123.

The RTP/RTCP datagram handler 2144 consists of an RTP/RTCP datagrambuffer and an RTP/RTCP datagram parser. The RTP/RTCP datagram handler2144 buffers the data of RTP/RTCP structure outputted from the UDPdatagram handler 2143, and then extracts A/V stream from the buffereddata, thereby outputting the extracted A/V stream to the A/V decoder2161. The A/V decoder 2161 decodes the audio and video streams outputtedfrom the RTP/RTCP datagram handler 2144 using audio and video decodingalgorithms, respectively. The decoded audio and video data is outputtedto the presentation manager 2170. Herein, at least one of an AC-3decoding algorithm, an MPEG 2 audio decoding algorithm, an MPEG 4 audiodecoding algorithm, an AAC decoding algorithm, an AAC+ decodingalgorithm, an HE AAC decoding algorithm, an AAC SBR decoding algorithm,an MPEG surround decoding algorithm, and a BSAC decoding algorithm canbe used as the audio decoding algorithm and at least one of an MPEG 2video decoding algorithm, an MPEG 4 video decoding algorithm, an H.264decoding algorithm, an SVC decoding algorithm, and a VC-1 decodingalgorithm can be used as the audio decoding algorithm.

The NTP datagram handler 2145 consists of an NTP datagram buffer and anNTP datagram parser. The NTP datagram handler 2145 buffers data havingan NTP structure, the data being outputted from the UDP datagram handler2143. Then, the NTP datagram handler 2145 extracts an NTP stream fromthe buffered data. Thereafter, the extracted NTP stream is outputted tothe A/V decoder 2161 so as to be decoded.

The service protection stream handler 2146 may further include a serviceprotection stream buffer. Herein, the service protection stream handler2146 buffers data designated (or required) for service protection, thedata being outputted from the UDP datagram handler 2143. Subsequently,the service protection stream handler 2146 extracts information requiredfor descrambling from the extracted data. The information required fordescrambling includes a key value, such as SKTM and LKTM. Theinformation for descrambling is stored in the second storage unit 2147,and, when required, the information for descrambling is outputted to thedescrambler 2142.

The ALC/LCT stream handler 2148 consists of an ALC/LCT stream buffer andan ALC/LCT stream parser. And, the ALC/LCT stream handler 2148 buffersdata having an ALC/LCT structure, the data being outputted from the UDPdatagram handler 2143. Then, the ALC/LCT stream handler 2148 analyzes aheader and a header expansion of an ALC/LCT session from the buffereddata. Based upon the analysis result of the header and header expansionof the ALC/LCT session, when the data being transmitted to the ALC/LCTsession correspond to an XML structure, the corresponding data areoutputted to an XML parser 2150. Alternatively, when the data beingtransmitted to the ALC/LCT session correspond to a file structure, thecorresponding data are outputted to a file decoder 2162.

At this point, when the data that are being transmitted to the ALC/LCTsession are compressed, the compressed data are decompressed by adecompressor 2149, thereby being outputted to the XML parser 2150 or thefile decoder 2162.

The XML parser 2150 analyses the XML data being transmitted through theALC/LCT session. Then, when the analyzed data correspond to datadesignated to a file-based service, the XML parser 2150 outputs thecorresponding data to the FDT handler 2151. On the other hand, if theanalyzed data correspond to data designated to a service guide, the XMLparser 2150 outputs the corresponding data to the SG handler 2165.

The FDT handler 2151 analyzes and processes a file description table ofa FLUTE protocol, which is transmitted in an XML structure through theALC/LCT session. The FDT handler 2151 is controlled by the servicemanager 2122 when the received file is the file for the NRT service. Thefile may include the disaster-related additional information.

The SG handler 2165 collects and analyzes the data designated for aservice guide, the data being transmitted in an XML structure, therebyoutputting the analyzed data to the service manager 2122.

The file decoder 2162 decodes the data having a file structure and beingtransmitted through the ALC/LCT session, thereby outputting the decodeddata to the middleware engine 2164 or storing the decoded data in athird storage unit 2163. According to an embodiment of the presentinvention, the data of a file structure that are decoded by the filedecoder 2162 include the NRT service data.

Herein, the middleware engine 2164 translates the file structure data(i.e., the application) like the NRT service and executes the translatedapplication. Thereafter, the application may be outputted to an outputdevice, such as a display screen or speakers, through the applicationpresentation manager 2170. According to an embodiment of the presentinvention, the middleware engine 2164 corresponds to a JAVA-basedmiddleware engine.

Based upon a user-input, the EPG manager 2171 receives EPG data eitherthrough the service manager 2122 or through the SG handler 2165, so asto convert the received EPG data to a display format, thereby outputtingthe converted data to the presentation manager 2170.

The application manager 2172 performs overall management associated withthe processing of application data (for example, NRT service data),which are being transmitted in object formats, file formats, and so on.

Furthermore, based upon a user-command inputted through the UI manager2173, the operation controller 2100 controls at least one of the servicemanager 2122, the EPG manager 2171, the application manager 2172, andthe presentation manager 2170, so as to enable the user-requestedfunction to be executed.

The UI manager 2173 transfers the user-input to the operation controller2100 through the UI.

Finally, the presentation manager 2170 provides at least one of theaudio and video data being outputted from the A/V decoder 2161 and theEPG data being outputted from the EPG manager 2171 to the user throughthe speaker and/or display screen.

It will be apparent to those skilled in the art that variousmodifications and variations can be made in the present inventionwithout departing from the spirit or scope of the inventions. Thus, itis intended that the present invention covers the modifications andvariations of this invention provided they come within the scope of theappended claims and their equivalents.

MODE FOR INVENTION

As described above, the present invention is described with respect tothe best mode for carrying out the present invention.

INDUSTRIAL APPLICABILITY

As described above, the present invention may be fully (or entirely) orpartially applied to broadcast and communication fields an embodiment ofa transmitting system, a receiving system and method of processing abroadcast signal according to the present invention.

What is claimed is:
 1. A method for processing a broadcast signal in atransmitting system, the method comprising: performing ReedSolomon-Cyclic Redundancy Check (RS-CRC) encoding on mobile servicedata, thereby generating an RS frame belonging to an ensemble; dividingthe RS frame into a plurality of RS frame portions; mapping the RS frameportions into each of data groups and inserting one fast informationchannel (FIC) segment and a plurality of known data sequences into eachof the data groups; performing trellis encoding on data of the datagroups; and transmitting the broadcast signal including thetrellis-encoded data, wherein an FIC chunk is configured with an FICchunk header and FIC chunk payload, signals binding information betweenthe ensemble and a mobile service included in the ensemble, and isdivided into a plurality of FIC segment payloads, wherein the FICsegment is configured with an FIC segment header and one of theplurality of FIC segment payloads, wherein the FIC segment headercomprises wake-up indication information which is used to determine at areceiver whether the receiver should wake up or not, wherein anemergency alert message is transferred through at least an emergencyalert table (EAT) or an Internet protocol (IP) datagram, and wherein theEAT includes information for indicating whether the emergency alertmessage is transferred through the EAT or the IP datagram.
 2. The methodaccording to claim 1, wherein the EAT further includes accessinformation for accessing the IP datagram when the emergency alertmessage is transferred through the IP datagram.
 3. The method accordingto claim 1, wherein the ensemble comprises at least one of a service maptable (SMT) describing the mobile service and the EAT, and wherein eachof the SMT and the EAT comprises an ensemble identifier to identify theensemble.
 4. The method according to claim 3, wherein IP datagramsincluding the SMT and IP datagrams including the EAT are transmittedover a service signaling channel, and wherein all the IP datagramstransmitted over the service signaling channel have a same well-known IPaddress and a same well-known user datagram protocol (UDP) port number.5. The method according to claim 4, wherein the SMT and the EAT areidentified using a table identifier included in each of the SMT and theEAT.
 6. The method according to claim 3, wherein the FIC chunk comprisesthe ensemble identifier to identify the ensemble.
 7. The methodaccording to claim 3, wherein at least one of the SMT and the EATfurther includes a non-real time (NRT) service identifier to identify anNRT service providing additional information associated with theemergency alert message.
 8. The method according to claim 7, wherein theadditional information comprises at least one of a text, an image and avideo associated with the emergency alert message.
 9. A transmittingsystem comprising: a first encoder circuit configured to perform ReedSolomon-Cyclic Redundancy Check (RS-CRC) encoding on mobile servicedata, thereby generating an RS frame belonging to an ensemble, a dividercircuit configured to divide the RS frame into a plurality of RS frameportions; a group formatting circuit configured to map the RS frameportions into each of data groups and insert one fast informationchannel (FIC) segment and a plurality of known data sequences into eachof the data groups; a second encoder circuit configured to performtrellis encoding on data of the data groups; and a transmitterconfigured to transmit a broadcast signal including the trellis-encodeddata, wherein an FIC chunk is configured with an FIC chunk header andFIC chunk payload, signals binding information between the ensemble anda mobile service included in the ensemble, and is divided into aplurality of FIC segment payloads, wherein the FIC segment is configuredwith an FIC segment header and one of the plurality of FIC segmentpayloads, wherein the FIC segment header comprises wake-up indicationinformation which is used to determine at a receiver whether thereceiver should wake up or not, wherein an emergency alert message istransferred through at least an emergency alert table (EAT) or anInternet protocol (IP) datagram, and wherein the EAT includesinformation for indicating whether the emergency alert message istransferred through the EAT or the IP datagram.
 10. The transmittingsystem according to claim 9, wherein the EAT further includes accessinformation for accessing the IP datagram when the emergency alertmessage is transferred through the IP datagram.
 11. The transmittingsystem according to claim 9, wherein the ensemble comprises at least oneof a service map table (SMT) describing the mobile service and the EAT,and wherein each of the SMT and the EAT comprises an ensemble identifierto identify the ensemble.
 12. The transmitting system according to claim11, wherein IP datagrams including the SMT and IP datagrams includingthe EAT are transmitted over a service signaling channel, and whereinall the IP datagrams transmitted over the service signaling channel havea same well-known IP address and a same well-known user datagramprotocol (UDP) port number.
 13. The transmitting system according toclaim 11, wherein the FIC chunk comprises the ensemble identifier toidentify the ensemble.
 14. The transmitting system according to claim11, wherein at least one of the SMT and the EAT further includes anon-real time (NRT) service identifier to identify an NRT serviceproviding additional information associated with the emergency alertmessage.
 15. The transmitting system according to claim 14, wherein theadditional information comprises at least one of a text, an image and avideo associated with the emergency alert message.